What is a catch-all email domain (and how to verify addresses on one)?
A catch-all email domain accepts mail for any address, real or not. How catch-all detection works, why these addresses are risky, and what to do with them.
A catch-all email domain is a domain whose mail server accepts mail for any address at that domain, whether or not a mailbox exists. Ask it about [email protected] and it says yes. Ask it about [email protected] and it also says yes. You’ll also see these called accept-all domains.
That matters because the standard way to check if an email address exists is to ask the domain’s mail server, and on a catch-all domain the answer is always yes. A verifier can’t confirm individual mailboxes there, so a good one reports them as risky, not as valid and not as invalid.
What happens to mail on a catch-all domain
“Accepts everything” describes what the server says during the conversation. What it does afterwards depends on the setup:
- Delivered to a shared inbox. Mail for unknown addresses goes to a designated mailbox, often watched by an office manager or IT. Somebody may read it, but not the person you meant.
- Bounced later. The server takes the message, finds no mailbox, and sends a bounce back to the sender. To a verifier it looked fine; to your sending reputation it’s a bounce.
- Quietly dropped. The message is accepted and discarded. No bounce, no reader.
- Delivered to the real person. For addresses that do exist, of course, mail arrives normally.
From the outside you can’t tell which of these applies. Neither can the verifier.
Why companies set it up
Catch-all is rarely a trick. It’s usually one of these:
- Not losing mail. Misspelled names, old addresses of people who left, addresses printed on old brochures: an accept-all rule makes sure nothing is refused.
- Small businesses and personal domains. Many hosting control panels offer a “default address” that catches everything, and owners switch it on so they can hand out a new address per website.
- Security gateways. Some email security services sit in front of the real mail server and accept every recipient, filtering and routing afterwards.
So an address on a catch-all domain is often a real person at a real company. Treating these as invalid would throw away good contacts.
How catch-all detection works
Detection uses the same SMTP conversation as any mailbox check, with one extra question. After asking about the real address, the verifier asks about one that can’t exist, a long random string at the same domain:
C: RCPT TO:<[email protected]>
S: 250 2.1.5 OK
C: RCPT TO:<[email protected]>
S: 250 2.1.5 OK <- a made-up address accepted too: catch-all
| Real address | Random address | Verdict |
|---|---|---|
| Accepted | Refused | Mailbox exists |
| Accepted | Accepted | Catch-all: can’t confirm the mailbox |
| Accepted | No clear answer (hang-up, “try later”) | Probably exists, lower confidence |
| Refused | (not asked) | No such mailbox |
Two details make the result more reliable:
- Ask about the real address first. Some servers drop the connection after one unknown recipient, to slow down address guessing. Asking the real question first means you have that answer even if the random one never gets one.
- Use the primary mail server. Backup MX servers often accept everything because they can’t see the user directory. A domain can look catch-all through its backup MX when its primary would have said no.
Catch-all is a property of the domain, so the result can be remembered for a while: once a domain has accepted a random address, there’s no need to ask its server again about every new address there.
What to do with risky catch-all results
It depends on where the address came from.
At sign-up
Send a confirmation email with a link. If the person clicks it, the address works and they own it. That settles it on catch-all domains as well as everywhere else. Don’t block sign-ups because their domain is catch-all.
On a list you’re about to email
- Keep catch-all addresses in their own segment rather than deleting them.
- Send to them in smaller batches at first and watch bounces and engagement.
- Drop the ones that bounce, and the ones that never open or click after a few sends.
- Check role addresses separately.
info@orsales@on a catch-all domain is very likely to reach someone, but not a specific person; see role-based email addresses.
In a CRM or lead list
The address may not prove there’s a person behind it, but the domain still tells you about the company. Whether acme.io is a business domain on Google Workspace or Microsoft 365 doesn’t depend on whether jane@ exists. Email verification vs classification explains how the two checks fit together.
Catch-all is not the same as these
A few setups look similar from the outside but behave differently:
- Role addresses.
info@,sales@andsupport@are real mailboxes that usually exist on purpose. A verifier answers for them like any other address; on a domain that isn’t catch-all, a250forinfo@really means the mailbox exists. - Aliases and groups.
[email protected]may be a distribution list that copies every message to several people. It is accepted because it exists, not because the domain accepts everything. Shared inboxes and Google Groups covers how to spot them. - Plus addressing.
[email protected]is accepted on many providers because the part after+is ignored for delivery. That’s a feature of the provider, not a catch-all rule, and a random address at the same domain is still refused. - Forwarding-only domains. A domain whose MX points at a forwarding service may accept and forward mail for any address to someone’s personal inbox. To a verifier this looks exactly like catch-all, and it is reported the same way.
- Greylisting. A server that answers “try again later” to everyone at first isn’t catch-all; it hasn’t answered yet. A careful verifier reports that as unknown and asks again later.
Why not just guess?
It’s tempting to call catch-all addresses “probably valid” and move on, especially when the name looks right. The trouble is that the same domain also accepts the typo, the person who left two years ago and the address someone invented to get past your form. Reporting all of them as deliverable would hide exactly the addresses you wanted to find.
Reporting them as invalid is worse: you’d reject real people at companies that made a reasonable configuration choice.
So the honest answer is a third one: risky. The address may well work, and you should decide how much that uncertainty matters for this particular use. For a password reset, it doesn’t: the person typed their own address and will tell you if nothing arrives. For a cold campaign to a bought list, it matters a lot, because bounces and spam complaints damage your sender reputation for every other message you send.
Catch-all in isBusinessEmail
The free email verifier and the /v1/verify endpoint run the random-address test on every check that gets a 250. When the domain accepts the random address, the result is:
{
"status": "risky",
"reason": "catch_all",
"mailbox": "unknown",
"is_catch_all": true,
"confidence": 0.5
}
When the random address is refused, is_catch_all is false and a 250 for the real address becomes deliverable with reason mailbox_exists. When the server gave no clear answer to the random address, is_catch_all is null and the result is deliverable with the lower-confidence reason accepted_unconfirmed. Catch-all domains are remembered for 12 hours, so later checks at the same domain don’t contact its server again. You can see the response shape without a key using [email protected].
Frequently asked questions
What does catch-all mean in email?
A catch-all (or accept-all) domain accepts mail for any address at that domain. Mail to a mailbox that doesn't exist is either delivered to a designated inbox, quietly dropped, or bounced later instead of being refused during the SMTP conversation.
Are catch-all email addresses valid?
Many are. A catch-all setup is a property of the domain, not of the address, so jane@ may be a real employee while jnae@ is a typo. A verifier can't tell them apart from the mail server's reply, so it reports both as risky or accept-all.
How do you know if a domain is catch-all?
Ask its mail server about an address that can't exist, such as a long random string, in the same SMTP conversation. If the server accepts it with a 250 reply, the domain accepts all recipients.
Should I remove catch-all addresses from my email list?
Not automatically. Remove them only if your bounce rate is already a problem. Otherwise keep them in a separate segment, watch their bounces and engagement, and drop the ones that bounce or never open.
Why do companies use catch-all email?
To avoid losing mail sent to misspelled or old addresses, to collect mail for former employees, or simply because their mail server or security gateway is configured to accept everything and filter later.
Can a catch-all address still bounce?
Yes. Some servers accept every recipient during the conversation and send a bounce message afterwards, once they find no matching mailbox. That is why a catch-all result is risky rather than deliverable.