What is a catch-all email?

How does a catch-all email domain work?

A catch-all domain changes one answer in the exchange between mail servers. A mail server reads the recipient address before it agrees to take a message. On most domains, an address that matches a mailbox gets a yes, the 250 reply, and an unknown one gets a no, usually a 550 reply, which the sender receives as a bounce (RFC 5321).

A catch-all domain answers yes to every address. Mail for a real mailbox reaches its owner. Mail for anything else, whether a typo, a former employee or a made-up name, goes to one shared mailbox chosen by an administrator.

Companies set it up so that misaddressed mail is not lost. Google’s help center gives an example: messages for role addresses such as support, help and info, all delivered to a single inbox (Google Workspace). It is a setting of the mail service, not of DNS. In Google Workspace, it is a routing rule for inactive and unrecognized accounts. Microsoft 365 starts from the opposite: for a domain whose mailboxes all live in Exchange Online, it rejects an unknown address at its edge with a 550 5.4.1 reply (Microsoft).

Can you verify a catch-all email?

A catch-all email cannot be verified with the standard check alone. Email verification tests an address without sending anything: it checks the syntax, looks up the domain’s MX record, then opens an SMTP conversation with that server and asks whether it would take mail for the address. On an ordinary domain, that last answer settles it.

On a catch-all domain, it settles nothing. The usual test is to ask the same server about an address that cannot exist, such as a long random string. If the server accepts that one too, every yes from the domain is worthless, and the address comes back as catch-all, accept-all, risky or unknown, depending on the tool.

Ordinary domainKnows its mailboxes

1. A made-up address
2. Reply 550
3. Refused: the check works

Catch-all domainSays yes to everything

1. A made-up address
2. Reply 250
3. Accepted: proves nothing

The SMTP standard adds a warning of its own. A server may accept a recipient during the conversation and check it later (RFC 5321, section 7.3); if delivery then fails, it has to send a bounce notice (section 6.1). An address on a catch-all domain can pass every check and still bounce.

Confirming one takes other evidence: a reply from the address, a record that ties that exact address to that person, or the person confirming it, as in a double opt-in.

Valid, invalid, catch-all and unknown: what is the difference?

An email verifier returns one of four results, depending on what the mail server says about the address and about a made-up one: valid, invalid, catch-all or unknown.

Result	What the mail server said	What it means	What to do
Valid	Yes to this address, no to a made-up one	The mailbox exists today	Send
Invalid	No to this address	The mailbox or the domain does not exist	Remove it: it would hard bounce
Catch-all	Yes to every address	The server cannot confirm this mailbox	Find other evidence before you send
Unknown	No clear answer, such as a timeout or a temporary refusal	The check did not finish	Try again later

Check yourselfA verifier asks a company's mail server about the address it wants to check, then about a random address that cannot exist. The server accepts both. What can you conclude?

• The address exists, so it is safe to send
• The domain is catch-all, and the address is unconfirmed
• The address is invalid and will bounce
• The domain has no MX record

Show the answer key

1. ✕The address exists, so it is safe to sendThe server also accepted an address that cannot exist, so its yes says nothing about this one.
2. ✓The domain is catch-all, and the address is unconfirmedA server that accepts a made-up address accepts everything. The result is catch-all, and only other evidence can confirm this mailbox.
3. ✕The address is invalid and will bounceNothing says it is wrong either. It may be a real mailbox; the check simply cannot tell.
4. ✕The domain has no MX recordA server answered for the domain, so its mail has somewhere to go. The problem is what the server says, not where it is.

Should you send to catch-all email addresses?

You can send to catch-all email addresses, carefully. A catch-all domain still has real mailboxes; the setting only hides which addresses they are.

• Keep them in their own segment, and never count them as verified.
• Prefer an address you have evidence for over one built from the company email format. On a catch-all domain, a guessed address passes the server check whether it exists or not.
• Send in small batches and watch the hard bounces. A server that accepted an address can still return the message later as an email bounce.
• Check again before each campaign. Administrators change the setting, and the work email of someone who leaves the company stops working.

How do you get a verified email on a catch-all domain?

To get a verified email on a catch-all domain, start from the person rather than from a pattern.

Email Enrichment takes a profile URL and returns a work email only when BlitzAPI holds a record of that address tied to that person; it never builds an address from a name and a format. According to its documentation, each address is checked with the receiving mail server before delivery, verified emails are tested again at least once every 30 days, and an address that fails a check is taken out of circulation. On a catch-all domain, the server’s yes settles nothing: what confirms the address is the record that ties it to the person. When no verified email exists, the response says found: false and no record is counted (API reference).