A catch-all lead is a lead whose email domain is configured to accept mail for any local part, so a verification probe cannot tell whether the specific mailbox exists. The address may be real or invented; the server says yes either way. In the 2026 corpus 2.3% of business addresses were catch-all overall, 12.4% on .org domains and 8.9% on tpg.com.au. Finders and most databases count them as found; a verifier labels them separately so they can be routed with care.
Catch-all is a property of the domain, detected by probing a random address that cannot exist; if the server accepts it, every address on that domain is unconfirmable by SMTP. Some verifiers add further signals to split catch-all addresses into likely and unlikely, but no probe can turn a catch-all into a confirmed valid.
Routing is the practical answer. Catch-all leads go into warm, low-volume sequences from a secondary domain, or to phone and LinkedIn, never into cold volume from the main domain. The catch-all email explainer covers the mechanics; the catch-all verification page covers what can and cannot be resolved.
A 3,000-row export from a non-profit database is verified. 410 addresses, 13.7%, come back catch-all, in line with the .org rate. They are sequenced at 20 a day from a secondary domain. Bounces on that domain run 6%, confirming that roughly one in sixteen catch-all addresses was a bad guess, while the main domain, sending only to confirmed valid, stays under 1%.
Verify a list or a single address. 100 free checks a month, unknowns refunded.
Verify Leads - FreeAyoub built BounceZero's 5-stage validation pipeline, its dedicated BGP-announced IP infrastructure, and the Patroni HA PostgreSQL cluster behind every verification. Previously built high-volume email delivery infrastructure. Trained at 1337 Benguerir (École 42 network, 2019). Open-source: bgp_analyzer.