Catch-all email
Catch-all email: what it is and should you send to it?
A catch-all email domain is configured to accept mail for every address, whether or not the mailbox exists. Because the server says yes to everything, no verifier can confirm that a specific address is real, so these addresses come back as Unknown.
By Steve Smith, EasyMailVerify team
Last updated · Editorial standards
No monthly subscription · Credits never expire · Unknown results use no credits
What is a catch-all email?
A catch-all email is an address on a domain that accepts mail for every address, whether or not that mailbox exists.
Normally a mail server rejects mail for mailboxes that don't exist. A catch-all (or accept-all) server accepts everything sent to the domain, so jane@company.com, j.ane@company.com and anything-at-all@company.com all look the same from outside. Companies use it so mistyped messages still reach someone.
Why catch-all addresses can't be confirmed
Email verification works by asking the receiving server whether a mailbox exists, without sending a message. A catch-all server answers yes for every address, so the answer carries no information about the specific mailbox.
How are catch-all domains detected?
A verifier tests the domain with an address that almost certainly doesn't exist. If the server accepts it too, the domain is catch-all, and every address on it is reported as Unknown rather than Passed.
Examples
| Address | Result | Why |
|---|---|---|
| info@globex-example.com | Unknown | The domain accepts every address |
| sarah@gmail.com | Passed | Gmail confirms individual mailboxes |
| sarah.typo@gmail.com | Failed | Gmail rejects mailboxes that don't exist |
How common are catch-all domains?
They're most common on company domains, so B2B lists usually contain far more catch-all addresses than lists of consumer Gmail, Outlook or Yahoo addresses.
What are the risks of sending to catch-all addresses?
- Some addresses don't belong to anyone and are silently dropped or bounce later
- You can't tell real contacts from typos on the same domain
- Mixing them into your main send hides which segment caused problems
Should you send to catch-all addresses?
| Situation | Suggested approach |
|---|---|
| Contact engaged recently | Send normally |
| Older contact or unclear source | Send to a small test segment first |
| Cold outreach | Send cautiously in small batches and watch bounces |
| High-value contact | Confirm through another channel |
A segmentation strategy that works

- Export Unknown results as their own list
- Send to that segment after your main send, in smaller batches
- Watch bounces and engagement, and keep only addresses that engage
How does EasyMailVerify handle catch-all emails?
Catch-all addresses are marked Unknown with the result code catch_all and a plain-language reason. The catch_all flag appears in exports and the API, and Unknown results use no credits, so you never pay for an answer that can't be given.
Frequently asked questions
What is a catch-all email address?
An address on a domain that accepts mail for any address, so the specific mailbox can't be confirmed.
Is a catch-all email valid?
It might be. The domain accepts mail, but there's no way to confirm that the specific mailbox is read by anyone.
Should I remove catch-all emails from my list?
Not automatically. Send to them as a separate segment in smaller batches and keep the ones that engage.
Why does my verifier mark catch-all emails as Unknown?
Because the server accepts every address, so it gives no answer about the specific mailbox. Reporting Unknown is more honest than guessing.
Do catch-all results cost credits?
Not with EasyMailVerify. Unknown results, including catch-all addresses, use no credits.
Sources
Related
Ready to check your list?
Pay only for Passed and Failed results. Credits never expire.
Create account