What is a catch-all email address?
Catch-all domains accept any mailbox name. Learn why we classify them as risky and how to handle them in B2B campaigns.
A catch-all (accept-all) mail server accepts every address on a domain — even doesnotexist@company.com. SMTP verification may return a positive handshake without proof that anyone reads the inbox.
Why catch-all is risky, not valid
The server can confirm the address at SMTP level, but:
- the message may be dropped silently,
- a hard bounce may only appear after you send a campaign,
- on large B2B lists catch-all increases uncertainty for opens and spam complaints.
In EmailVerifier catch-all is risky — a business decision, not auto-remove or auto-send.
When to send vs remove
| Scenario | Practice |
|---|---|
| Cold email at scale | Consider removing catch-all or testing in a small segment |
| Customer newsletter | Often acceptable if the address came from a legitimate source |
| Signup / trial | Prefer a real inbox; catch-all can hide throwaway signups |
| Re-engaging old lists | Remove catch-all with invalid to reduce bounce risk |
How detection works
We probe several random aliases on the same domain. If the server accepts all, we flag catch-all. Some servers behave oddly, which is why you may also see unknown on timeouts.
Next steps in the dashboard
- Upload CSV or call verify API.
- Filter status = risky with catch-all reason.
- Choose: test segment, remove, or manual review for key accounts.
One credit = one verification. Pay-as-you-go with no subscription — ideal for pre-campaign audits.