Home / Outbound Benchmarks / Catch-all detection test

Which email verifiers actually detect catch-all domains? The invented-address test

A one-minute test any team can replicate: verify a made-up address on domains known to accept everything. A verifier that answers 'valid' is not probing catch-all. Results for BillionVerify, AgentsVerify and No2Bounce.

Key finding: A random, non-existent local part sent to accept-all domains came back 'valid, is_catchall=false' from BillionVerify on 9 of 9 domains (August 2026) and 'invalid' from AgentsVerify on 10 of 10 (October 2026). No2Bounce does not call it valid but returns 'Deliverable/AcceptAll, catchall=true' with a score of 99, which is the same as saying 'cannot decide'.
Measured onOctober 26, 2026
Sample9 catch-all domains (August test) and 10 catch-all domains (October test), 1 invented address each; 307 confirmed catch-all addresses re-submitted to No2Bounce (September)
MethodDomains identified as accept-all by a first verifier. For each, an address of the form random-string.nobody@domain was submitted with SMTP checking and cache refresh forced. Any 'valid' answer is a false positive by construction.
SourceVision Media internal measurement (campaign and API logs)
Invented address on accept-all domains
VerifierDomains testedAnswer on an address that cannot existInterpretation
BillionVerify9'valid', smtp_deliverable, is_catchall=false on 9 of 9No random-recipient probe; a single 250 OK is enough
AgentsVerify10'invalid' on 10 of 10Real catch-all probe
No2Bounce307 confirmed catch-all addresses'Deliverable/AcceptAll', catchall=true, score 99 on 307 of 307Flags the domain; does not decide the address

Why this matters more than the vendor's accuracy claim

On B2B lists built from discovery databases, 26 to 48% of the addresses sit on catch-all domains in our pools (see the related measurement on discovery data). A verifier that calls every one of them 'valid' reports a 95% pass rate on a list that will bounce at 15 to 20%. The invented-address test exposes that in one API call per domain, before any credits are spent on the full list.

What 'catch-all' costs when you resubmit it

In September 2026 we re-submitted 307 addresses already marked catch-all by a first verifier to No2Bounce, hoping to rescue some of them. Result: 0 rescued out of 307; every one came back 'Deliverable/AcceptAll, catchall=true, score 99'. 307 credits for zero information. A confirmed catch-all is not an 'unknown': re-verifying it with a tool that does not probe only reconfirms what you already know.

How to run the test yourself

  1. Take 10 domains your current verifier marks as catch-all or accept-all.
  2. Submit an address like zq7x9random.nobody@domain with SMTP check and cache refresh forced.
  3. Count how many come back 'valid'. Anything above zero means the tool is not probing; its catch-all rate on your list is unknown.

What this measurement does not say

Questions

What does catch-all mean for cold email?

The recipient's mail server accepts every address at the SMTP stage, so a verifier cannot tell whether the mailbox exists. In our B2B pools, catch-all addresses bounce at roughly 20 to 30% when sent without any further filtering.

Related measurements

Want this run on your pipeline?

We operate multichannel outbound (cold email, LinkedIn, paid retargeting, newsletters) for B2B companies, and we measure it the way these pages do.

Book a call