I tested 3 ways to verify catch-all email addresses — here's what actually works
Somewhere between a quarter and a third of the addresses on a typical B2B list sit on catch-all domains. I know this because I build an email validation API, and catch-all is the question every user eventually asks: "Yo
Somewhere between a quarter and a third of the addresses on a typical B2B list sit on catch-all domains. I know this because I build an email validation API, and catch-all is the question every user eventually asks:
"Your API says this address is fine. But the domain is catch-all — so is the mailbox real or not?"
The honest answer is that nobody can tell you that from the outside. But "nobody can" is not what the verification industry advertises, so I spent some time testing the three approaches that are actually sold as catch-all verification, using real domains and my own API's live output. Here's what each one really does.
What "catch-all" means, in one paragraph
A catch-all (accept-all) mail server is configured to accept mail for any local part at the domain — real employees, people who left years ago, and addresses that never existed. It's a deliberate, legitimate setup, common at companies that would rather receive a mis-addressed message than lose it. Google Workspace and Microsoft 365 both let admins enable it, which is why so much of B2B email lives behind it.
The consequence: from the outside, every address at that domain looks identical. And that breaks the standard verification playbook.
Way 1: SMTP probing — the server says yes to everything
The classic verification trick is to open an SMTP conversation with the receiving server, start a delivery to the address in question, and read the response code — then hang up before sending anything. A 250 means "accepted", a 550 means "no such mailbox".
On a normal domain this works reasonably well. On a catch-all domain it proves nothing, by definition: the server answers 250 for the CEO's real address and for totally-invented-zzq@ with exactly the same enthusiasm. The probe tells you the server accepts mail — which you already knew from its MX records.
There's also a practical problem nobody mentions: outbound port 25 is blocked or throttled in most cloud and corporate networks, so running your own probes at scale means fighting your infrastructure provider before you fight the data.
Verdict: on catch-all domains, an SMTP probe returns a confident-looking answer that contains zero information about the mailbox.
Way 2: Big-vendor scoring — better, but look at the resolution rates
The large verification vendors know probing fails on catch-all, so they layer scoring on top: domain age, provider patterns, and — the part you can't replicate — engagement data from their own sending networks (did this address open, click, bounce somewhere else before?).
Some of that is genuinely useful. But published benchmark figures for how often vendors actually resolve a catch-all address to a firm verdict are sobering: roughly 12% for ZeroBounce, 8% for NeverBounce, 5% for MillionVerifier. In other words, the best-known vendor in the industry settles about one catch-all address in eight. The other seven come back as some flavour of "unknown" — usually at the same per-address price as a resolved one.
Verdict: real signal, but you're paying full price for a coin that lands on its edge 7 times out of 8.
Way 3: Domain-level signals — grade the risk, don't fake the verdict
The third approach gives up on the mailbox question entirely and answers a different, answerable one: what kind of domain is this, and how much risk does an address on it carry?
This is what I built into my own API (EmailCheck), so let me show you real output instead of describing it. I ran one batch call with 10 addresses chosen to cover the signal space — consumer providers, corporate domains, a disposable service, a typo, a domain that doesn't exist:
| Address | Verdict | Score | catchAllRisk | Domain age (days) |
|---|---|---|---|---|
| [email protected] | valid | 100 | low | 11,417 |
| [email protected] | valid | 100 | low | 11,777 |
| [email protected] | valid | 90 | unknown | 10,653 |
| [email protected] | valid | 100 | unknown | 10,653 |
| [email protected] | valid | 100 | possible | 12,981 |
| [email protected] | valid | 90 | possible | 11,387 |
| [email protected] | valid | 100 | possible | null (no RDAP record) |
| [email protected] | risky | 50 | possible | 8,536 |
| [email protected] | risky | 60 | possible | 10,366 |
| [email protected] | invalid | 15 | unknown | — |
Four rows in that table taught me more than the marketing pages of every vendor combined:
The invented address passes. [email protected] is an address I made up; it scores 100. Domain-level checks verify the domain — its syntax, its MX records, its age — not the mailbox. Any tool that implies otherwise for a catch-all domain is selling you a score dressed up as a verdict. The correct output is the graded signal in the catchAllRisk column: possible for business-mail patterns where catch-all is commonly enabled (Microsoft 365 tenants, Google Workspace domains like stripe.com and linear.app), low for the big consumer providers.
The typo domain accepts mail too. [email protected] is a typo of Gmail — and gamil.com has its own MX records and has existed for 10,366 days. Typosquatter domains accept mail (that's the point of them), so "the domain accepts mail" can never be your only check. The API flags it as a likely typo, caps the score at 60, and returns the correction ([email protected]) in the suggestion field.
Disposable services are true catch-alls. Mailinator accepts literally everything — that's its product. It comes back risky at 50: disposable flag set, catch-all risk possible. Both signals are true at once, and both matter for a signup form.
Missing data is returned as missing. [email protected] has domainAgeDays: null because RDAP has no registration record the API could read. The field doesn't estimate, doesn't interpolate — it says null and names its source when it has one. I'd rather ship a null than a confident guess, because every downstream decision (send / segment / drop) inherits whatever the API claims.
Here's the raw response for the typo row, so you can see the full shape:
{
"email": "[email protected]",
"valid": true,
"score": 60,
"verdict": "risky",
"checks": {
"syntax": true,
"domainExists": true,
"mxFound": true,
"disposable": false,
"roleAccount": false,
"freeProvider": false
},
"mxRecords": ["mail.gamil.com"],
"suggestion": "[email protected]",
"typoLikely": true,
"domainAgeDays": 10366,
"domainAgeSource": "RDAP",
"catchAllRisk": "possible"
}
Verdict: you don't get a yes/no on the mailbox — nobody honestly has one — but you get an auditable risk picture per address, which is what list decisions actually need.
What to actually do with catch-all addresses
After all this testing, my working rules are boring and practical:
- Don't delete them. If 30% of your B2B list is catch-all, deleting them deletes your market. The big vendors' own numbers say most of those addresses are simply unresolvable, not fake.
- Segment them. Send to catch-all addresses as their own cohort, after your clean addresses, so a bad pocket can't drag your main sender reputation down with it.
- Let bounces teach you. A hard bounce from a catch-all domain is real information — that mailbox genuinely doesn't exist. Feed those back into your list; it's the one ground truth this problem gives you.
- At signup, act on the other signals. Disposable flag, two-day-old domain, typo suggestion — those are actionable in real time, catch-all or not.
The tool, briefly
EmailCheck is live on RapidAPI with a free tier (100 calls/month), single and batch endpoints (up to 100 addresses per call, with a summary report), and the fields you saw above on every response. There's also a free bulk checker and a $9.99 pack of 3,500 checks if you'd rather not think about subscriptions.
- EmailCheck on RapidAPI: https://rapidapi.com/binbin7418/api/emailcheck-email-validation-api
- Free bulk checker: https://email.newkwlab.com/bulk-email-checker/
- The longer catch-all write-up: https://email.newkwlab.com/questions/can-a-catch-all-email-address-be-verified/
- The $9.99 pack (3,500 checks): https://binbinster.gumroad.com/l/newkwlab-credits-3500
If you verify email for a living, I'd genuinely like to hear how you treat catch-all addresses. The industry mostly pretends this problem is solved. It isn't, and the pretence is priced per address.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.