- False-positive rate, defined
- A false-positive rate in email verification is the share of addresses a verifier marks valid that still bounce or never reach a mailbox once you send.
Every verifier makes two kinds of mistake. A false positive calls a dead address valid, and you find out when it hard bounces. A false negative calls a working address invalid, and you quietly lose a real contact. Senders feel the first one far more, because bounces are what mailbox providers count against you.
Here's where most false positives come from: servers that say yes to everything. A catch-all domain answers 250 for any address you try, so a tool that folds catch-alls into valid is guessing on every one of them. Yahoo and AOL do the same on purpose, then bounce the message later.
Timing adds a few more. An address can pass today and be closed next month when its owner leaves the company, so a list checked in spring and mailed in autumn shows false positives the verifier never made.
Vendor figures don't settle it. ZeroBounce claims 99.6% accuracy and Reoon claims over 99%, both read on their own sites in September 2026. Hunter's benchmark of 3,000 real business addresses across 15 verifiers, dated 3 November 2025, measured overall accuracy between 31.2% and 70.0%. Both can be true because they divide by different things.
So ask for the false-positive rate on its own line, beside the share of the list that got a verdict. A tool that reaches a verdict on 60% of your file with almost no false positives is more use to you than one that calls 95% valid and lets the bounces sort it out. The two numbers every verifier hides works through the arithmetic.
You can measure your own. Send to a small slice of freshly verified valid addresses, count the hard bounces over 72 hours, and divide by the number sent. Your bounce rate on verified rows is the false-positive rate you actually pay for.
How ZapBounce reports it
ZapBounce states accuracy with the false-positive rate on its own line, next to coverage, the share of your list that reached a verdict. A catch-all address comes back as catch_all and never as valid, so the biggest source of false positives in the market stays out of your valid column. Rows the server wouldn't answer come back unknown and are never billed. The accuracy page sets out how those numbers are measured.
False-positive rate: common questions
What is a good false-positive rate for email verification?
Low enough that your verified sends stay under a 2% bounce rate. Anything that pushes a clean send past that line means valid results are being handed out too freely, usually on catch-all domains.
Is false-positive rate the same as accuracy?
No. Accuracy counts every correct verdict, both yes and no, while the false-positive rate counts only the addresses wrongly called valid. A tool can post high accuracy and still pass a lot of dead addresses if its denominator leaves out catch-alls and unknowns.
What is a false negative in email verification?
A working address marked invalid. It costs you a contact rather than a bounce, and it usually comes from a server that blocked or throttled the probe and got read as a no.
Why don't verifiers publish their false-positive rate?
Most publish one accuracy figure instead, measured on the addresses they resolved. The false-positive rate depends heavily on how a tool treats catch-all domains, which is the part a single percentage hides.