Guide
Email Verifier Accuracy: What the Numbers Really Mean and How to Test Them
By Unlimited Verifier Team ·

Summary
Email verifier accuracy is the share of addresses a tool correctly labels deliverable or undeliverable. Reputable verifiers usually reach about 95–99% on decisive Valid/Invalid results, but many '99%' claims exclude catch-all and unknown addresses. The metric that matters most is your hard bounce rate after verification: aim for under 1%.Email verifier accuracy is the percentage of addresses a tool classifies correctly as deliverable or undeliverable. Reputable verifiers typically land around 95–99% on the results they are willing to call, but most "99%" claims leave out catch-all and unknown addresses.
That gap between the advertised number and real-world performance is what this guide covers. You will learn what accuracy measures, why two tools give different verdicts on the same address, where every verifier struggles, and how to test a tool on your own list before you trust it with your sender reputation.
Quick answer
- Realistic accuracy: expect roughly 95–99% correct on decisive (Valid/Invalid) results. Treat any figure above 99% as a vendor claim measured on that vendor's own test data. Unlimited Verifier, for example, states 99.5% accuracy for its deep verification.
- The metric that matters: your hard bounce rate after verification. Aim for under 1%. Treat 2% as the ceiling most deliverability practitioners work to.
- The hidden variable is coverage. A tool can look more "accurate" by labelling hard cases Unknown or Risky. Always read accuracy alongside the unknown/risky rate.
- Accuracy breaks down in predictable places: catch-all domains, greylisting servers, some Microsoft 365 tenants, and old data. No verifier can guarantee zero bounces.
- Test before you commit: run a seed list plus a real sample of your data through each candidate, then compare their disagreements against actual send results.
What does "email verifier accuracy" actually mean?
Accuracy is how often a verifier's verdict matches what actually happens when you send: does a "Valid" address accept mail, and does an "Invalid" address hard-bounce? It is a measure of agreement with ground truth, and ground truth only exists once a real message is sent.
If you are new to the mechanics, start with what is email verification: the layered process of checking syntax, domain, MX records and the SMTP mailbox without sending an email. Accuracy describes how well that process predicts the outcome of a real send.
How do email verifiers measure accuracy?
Most vendors compute accuracy against a labelled test set. This is a list of addresses where the true status is already known, usually from controlled sends or from bounce logs. The verifier's output is compared to those labels.
The catch is in what gets counted. There are three common formulas, and vendors rarely say which one they use:
| Formula | What it counts | Why it can mislead |
|---|---|---|
| Decisive accuracy = correct Valid + correct Invalid ÷ (all Valid + Invalid verdicts) | Only addresses the tool committed to | Inflates if hard cases are pushed into Unknown/Risky |
| Overall accuracy = correct verdicts ÷ all addresses tested | Treats Unknown as "not correct" | Honest, but rarely published |
| Bounce-based accuracy = 1 − (bounces among "Valid" ÷ total "Valid") | Only the false-valid side | Ignores good addresses wrongly marked Invalid |
The deep dive on how email verifiers measure accuracy walks through each formula with examples. The practical takeaway: when a vendor quotes one number, ask which denominator it uses.
What is a false positive in email verification?
Terminology is inconsistent across the industry. Most vendors use false positive to mean an address marked deliverable that then bounces. Some statisticians and a few vendors use it the other way round. To avoid confusion, this guide uses plain labels:
- False valid: a bad address marked Valid. You send, it hard-bounces, and your reputation takes the hit.
- False invalid: a good address marked Invalid. You suppress it and lose a real customer silently.
See what a false positive is in email verification for the full definition and typical causes, such as mailboxes deleted after verification or servers that accept every recipient.
False positives vs false negatives: which costs more?
The two errors carry different costs, and the right trade-off depends on your business.
- False valids cost deliverability. Every hard bounce tells mailbox providers your list hygiene is poor. Bounce rates that climb past a few percent can trigger ESP account reviews.
- False invalids cost revenue. A B2B team that suppresses 3% of real decision-makers loses pipeline. Nobody notices, because suppressed contacts never complain.
A cold-outreach agency protecting sending domains should tolerate more false invalids. A SaaS company emailing paying customers should tolerate almost none. The comparison of false positives vs false negatives in email verification shows how to set your threshold for each.
Bottom line: "accuracy" is two error rates plus a coverage rate. Any single headline number hides at least one of them.
How accurate is email verification, really?
On the addresses it commits to, a well-built verifier is right the large majority of the time, typically in the mid-to-high 90s. Accuracy drops on the hard subset: catch-alls, greylisting servers and stale data. The full breakdown is in how accurate email verification really is.
A hard ceiling exists because verification happens before the send. The SMTP check opens a conversation with the receiving server and asks, through the RCPT TO command defined in RFC 5321, whether it would accept mail for a mailbox. Then it disconnects without sending. Three things can make that answer differ from what happens on a real send:
- The server answers optimistically. Catch-all (accept-all) servers say yes to every address and bounce later, or never.
- The server refuses to answer clearly. Greylisting, rate limits and anti-probe defences return temporary
4xxcodes or block the verifier's IP. - The world changes after the check. Mailboxes get deleted, employees leave and domains expire.
Do email verifiers really have 99% accuracy?
Some do on their own test sets, and few do on every list. A 99% figure is plausible when the denominator excludes catch-all and unknown addresses and the test list is mostly consumer webmail with clean SMTP responses. On a B2B list heavy with corporate domains and catch-alls, the same tool can perform noticeably worse in overall terms.
This doesn't mean the vendors are lying. Accuracy depends heavily on the dataset. The article on whether verifiers really hit 99% accuracy explains how to read these claims. Unlimited Verifier states 99.5% accuracy for its deep verification. Like any vendor figure, treat it as a starting hypothesis to confirm on your own data, using the testing framework later in this guide.
Are vendor accuracy claims trustworthy?
They are trustworthy as marketing claims and unreliable as purchasing evidence. Vendors choose the test set, the formula and the definition of "correct," and almost none publish all three. Three questions separate solid claims from slogans:
- Is the methodology published? Look for test-set size, composition (B2B/B2C mix, catch-all share) and how ground truth was established.
- Is the unknown/risky rate published alongside it? Accuracy without coverage is meaningless.
- Can you inspect the logic? A transparent engine lets you see how verdicts are produced. Unlimited Verifier's verification engine is open source on GitHub (unlimitedverifier/free-email-verifier), so the classification logic can be inspected rather than taken on faith.
The full checklist is in are vendor accuracy claims for email verifiers trustworthy.
What accuracy rate should an email verifier have?
Judge a verifier on outcomes you can measure, not the headline percentage. These are the thresholds this guide recommends, applied to your own data:
| Metric | Recommended target | Why this number |
|---|---|---|
| Hard bounce rate on "Valid" addresses | < 1% (ceiling 2%) | 2% is the widely used practitioner ceiling. Under 1% leaves headroom for decay between verification and send |
| False-invalid rate (good addresses suppressed) | < 1–2% | Above this, you're discarding real contacts at a material scale |
| Unknown rate, excluding catch-all | < 3–5% | Higher suggests the verifier's infrastructure is being blocked or timing out |
| Catch-all share | Report separately; no "good" number | It reflects your list's domains, not the verifier's quality |
Sources disagree on bounce ceilings. Some practitioners use 2%, others insist on 1%, and individual ESPs set their own review triggers. Recommendation: target under 1% and treat 2% as a hard stop. More on setting these thresholds in what accuracy rate an email verifier should have.
Bottom line: expect high-90s accuracy on decisive results. Judge tools by post-send bounce rate and unknown rate, not by the number on their homepage.
How does a verifier decide, and where does each step go wrong?
Every verifier runs a similar pipeline. Accuracy differences come from how carefully each stage handles edge cases.
| Check | What it catches | Typical failure mode |
|---|---|---|
| Syntax | Typos, illegal characters, missing @ |
Over-strict rules reject rare but valid formats (plus-addressing, unusual TLDs) |
| Domain / DNS | Nonexistent or expired domains | Brief DNS outages misread as "domain doesn't exist" |
| MX records | Domains that can't receive mail | Domains using fallback A-record delivery mishandled |
SMTP mailbox (RCPT TO) |
Nonexistent mailboxes (550 5.1.1) |
Greylisting, IP blocks, timeouts produce Unknowns |
| Catch-all detection | Servers that accept any address | Accept-all status changes; probes can be blocked |
| Disposable detection | Temporary inbox services | New disposable domains appear constantly; lists lag |
| Role-based detection | info@, sales@, support@ |
These are often valid; the flag signals risk, not invalidity |
Two details matter for accuracy. First, the response code 5.1.1 ("bad destination mailbox address") comes from RFC 3463, and it is the cleanest Invalid signal available. Anything else involves interpretation. Second, role-based and disposable flags are risk signals, not accuracy verdicts. A tool that marks every info@ Invalid will look "safe" but generates false invalids.
Unlimited Verifier runs all of these checks: syntax, domain, MX and SMTP mailbox, plus catch-all detection and disposable and role-based flags. It sorts every address into Valid, Risky or Invalid, so ambiguous results are kept separate from confirmed Valids. You can watch the pipeline on a single address with the free email checker before uploading anything.
Bottom line: the SMTP stage is where accuracy is won or lost. A verifier's quality shows in how it handles ambiguous server responses, not the easy ones.
Why do different email verifiers give different results?
Different verifiers return different verdicts because they talk to mail servers from different IP addresses, at different times, with different retry rules and different policies for labelling ambiguous answers. The same mailbox can produce different SMTP responses for different probes. The full explanation is in why different email verifiers give different results. The main causes:
- IP reputation and blocking. A server that blocks or throttles one verifier's IP range will look "Unknown" to that tool and answer normally for another.
- Timing and greylisting. A greylisting server rejects the first attempt temporarily. A verifier that retries later gets a real answer, while one that gives up returns Unknown.
- Catch-all labelling philosophy. Some tools report catch-all as its own category. Others score catch-all addresses with extra signals or fold them into Risky. Same address, different label.
- Live checks vs cached data. A tool that reuses a recent result may be faster but staler than one that checks live.
- Category schemes. One tool's "Risky" may be another's "Unknown" or "Do not mail." Mapping categories across tools is half the work of any comparison.
Why do ZeroBounce and NeverBounce disagree on the same email?
They are two widely used verifiers with different category systems and infrastructure, so disagreement is normal. Based on public documentation, ZeroBounce's statuses include categories such as valid, invalid, catch-all, unknown, spamtrap, abuse and do_not_mail. NeverBounce uses a shorter set (valid, invalid, disposable, catchall, unknown). An address ZeroBounce flags "abuse" may be "valid" to NeverBounce, and neither tool is wrong. They are answering different questions. Infrastructure and timing explain the rest. The specific patterns are unpacked in why ZeroBounce and NeverBounce disagree on the same email.
Practitioner insight: when two tools disagree, the disagreement set is where your accuracy decision gets made. Addresses both tools mark Invalid are almost certainly dead. Addresses both mark Valid are probably fine. The 5–15% where they split is what to test with a real send.
Bottom line: disagreement between verifiers is expected. Resolve it with send data, not by trusting whichever tool you used first.
Where does verifier accuracy break down?
Accuracy is uneven across a list. It is strong on major consumer webmail and clearly nonexistent domains, and weak on catch-alls, aggressively protected corporate servers and old data. Knowing where the weak spots are tells you where to apply extra caution.
What is a good unknown rate for an email verifier?
On a typical mixed list, aim for an unknown rate under 3–5%, excluding catch-all addresses, which should be reported separately. B2C lists dominated by large webmail providers often come in lower, while B2B lists with many self-hosted or heavily protected servers run higher. A persistently high unknown rate across different lists usually points to the verifier's infrastructure, not your data. Benchmarks by list type are in what a good unknown rate is for an email verifier.
Why does my verifier return so many unknowns?
The usual causes, in rough order of frequency:
- Greylisting: the server deferred the probe and the verifier didn't retry.
- Rate limiting or IP blocking: the verifier probed one domain too fast, or its IPs are flagged.
- Timeouts: slow servers that never completed the SMTP conversation.
- Temporarily unavailable servers: maintenance or outages.
The fix is often simple: re-verify the Unknowns 24–72 hours later. Greylisting and temporary blocks frequently clear, and a meaningful share of Unknowns resolve into decisive results. Troubleshooting steps are in why your verifier returns so many unknowns.
How accurate are email verifiers on catch-all domains?
Not very, and no verifier can be fully accurate here. A catch-all server returns "accepted" for every address, real or invented, so an SMTP check can't separate jane@company.com from xq7z@company.com. Verifiers detect catch-all status by probing a random, almost certainly nonexistent address. If that address is accepted, the whole domain is flagged.
What happens next varies. Some tools stop at the flag. Others add signals such as address patterns or historical engagement to estimate risk. In many B2B lists, a sizeable minority of addresses sit on catch-all domains, so how you handle them affects results materially. Recommended approach:
- Never treat catch-all as Valid by default.
- Send to catch-all segments separately, in small batches, from a well-warmed domain, and suppress anything that bounces.
- Prioritise by value: a catch-all address for a known customer is worth the risk. A catch-all address from a scraped list usually isn't.
Unlimited Verifier detects catch-all domains so these addresses don't hide inside your Valid count. Its catch-all verification page explains how they are handled. For the deeper analysis, read how accurate verifiers are on catch-all domains.
How accurate are email verifiers on Microsoft 365 addresses?
Results vary by tenant, because Microsoft 365 behaviour depends on each organisation's configuration. When Exchange Online's Directory-Based Edge Blocking is active, unknown recipients are rejected at the SMTP stage, which is ideal for verification. Microsoft's anti-abuse throttling can also defer or block high-volume probes, which pushes results toward Unknown, and some tenant configurations behave in ways that are harder to read.
The practical consequence: B2B lists heavy in corporate Microsoft 365 domains usually show more Unknowns and Risky results than consumer lists. See how accurate verifiers are on Microsoft 365 addresses.
Is verifier accuracy different on Gmail vs Outlook addresses?
Usually, yes. Gmail generally gives clear SMTP answers, rejecting nonexistent mailboxes with a definitive 5.1.1, so verifiers tend to perform well on @gmail.com. Consumer Outlook/Hotmail addresses tend to be harder: throttling of verification traffic is more common, producing more Unknowns. Some other consumer providers have at times accepted recipients at the SMTP stage and bounced later, which turns them into effective catch-alls.
This is why a verifier's accuracy on one list predicts little about another with a different provider mix. Provider-by-provider patterns are in email verifier accuracy on Gmail vs Outlook addresses.
Bottom line: segment your results by domain type. Catch-all and corporate Microsoft 365 segments need different handling from Gmail, and a blended accuracy number hides the difference.
Does a "Valid" result guarantee the email will be delivered?
No. "Valid" means the mailbox exists and the server said it would accept mail at the moment of the check. It says nothing about whether your message will reach the inbox. The distinction is covered fully in does a valid result mean the email will be delivered.
Deliverability (reaching the server) and inbox placement (avoiding the spam folder) are separate problems. Placement depends on authentication (SPF, DKIM, DMARC), sender reputation, content and engagement. Google's email sender guidelines require bulk senders to authenticate mail and keep reported spam rates below 0.3%, and Yahoo's sender best practices set similar expectations. Verification supports these goals by cutting bounces. It doesn't replace them. For the wider picture, see the email deliverability guide.
Can an email verifier guarantee zero bounces?
No legitimate verifier can guarantee zero bounces. Catch-all servers, mailboxes deleted after verification, full inboxes and server-side policy changes all produce bounces that no pre-send check can foresee. Some vendors offer bounce-rate guarantees with specific conditions attached, so read the terms. The reasoning is laid out in can an email verifier guarantee zero bounces.
What bounce rate should you expect after verification?
On addresses marked Valid and sent to promptly, a hard bounce rate well under 1% is a reasonable expectation for most lists. Bounces will run higher if you include catch-all/Risky addresses or wait weeks before sending. If you mail Valids and see more than 2%, something is wrong: the verification is stale, the verifier is weak, or catch-alls leaked into the Valid segment. Benchmarks by segment are in what bounce rate to expect after email verification.
How long do email verification results stay accurate?
Results start decaying the day you get them. Studies generally put B2B contact data decay at roughly a fifth to a third of a list per year as people change jobs, with consumer lists decaying more slowly. Practical rules of thumb:
- Verify within a few days of sending any list that has sat unused for 3+ months.
- Re-verify active lists quarterly (monthly for high-turnover B2B segments).
- Always verify imported, purchased-from-partner or event-sourced lists before first send.
The decay curve and re-verification schedule are covered in how long verification results stay accurate.
Bottom line: "Valid" means "exists right now." Pair verification with authentication and timely sending, and expect a small residual bounce rate.
How to test an email verifier's accuracy yourself
The only accuracy figure you can fully trust is one measured on your own data. This framework works for one tool or several. The step-by-step version is in how to test an email verifier's accuracy yourself.
The 7-step accuracy testing framework
- Define what "correct" means for you. Decide which matters more, false valids or false invalids, and set your thresholds (e.g., bounce < 1%, false invalid < 2%).
- Build a seed list of addresses whose true status you know (see below).
- Draw a real sample from your actual database, randomly selected, sized using the math below.
- Run every candidate verifier on the same day on the same files. Results drift over days, so same-day testing removes timing bias.
- Map categories to a common scheme: Valid / Invalid / Risky-or-Unknown / Catch-all.
- Score the seed list directly, since you know the answers. Then build a disagreement set from the real sample.
- Establish ground truth on the disagreement set with a careful send to opted-in contacts from a warmed domain, or by matching against recent bounce logs. Then calculate each tool's error rates.
How do you build a seed list to benchmark email verifiers?
A seed list is a controlled set of addresses with known status. A useful one includes:
- Known-good mailboxes you control on several providers (Gmail, Outlook, a Microsoft 365 tenant, a self-hosted server).
- Known-bad addresses: random strings on domains you know reject unknown recipients.
- Catch-all addresses on a domain you configure as accept-all, both real and invented.
- Edge-case syntax: plus-addressing, subdomains, long TLDs.
- Dead domains: recently expired or nonexistent domains.
Keep it small and precise. Around 100–150 addresses is enough to catch systematic mistakes. One practical note: Unlimited Verifier's Free plan accepts lists of up to 150 emails, so a seed list of this size fits in a single upload. Full instructions are in how to build a seed list to benchmark email verifiers.
How many emails should you use when testing a verifier?
Enough to make the bounce-rate estimate statistically meaningful. Bounce rate is a proportion, so the standard sample-size formula applies: n = z² × p(1−p) ÷ E², where z = 1.96 for 95% confidence, p is the expected bounce rate and E is the margin of error.
Worked through for an expected bounce rate of 1% among Valids:
- Margin ±0.5%: n = 3.8416 × 0.0099 ÷ 0.000025 ≈ 1,521 Valid addresses
- Margin ±0.3%: n = 3.8416 × 0.0099 ÷ 0.000009 ≈ 4,226 Valid addresses
So to tell whether a verifier really delivers under 1% bounces, you need roughly 1,500–4,000 addresses marked Valid and then sent to. That means a raw sample of a few thousand after accounting for Invalids and Risky results. A 200-address test can't distinguish a 0.5% bounce rate from a 1.5% one. Details are in how many emails to use when testing a verifier.
How do you run a side-by-side email verifier test?
Run two or more tools on the identical file, align their outputs, and focus your send budget on where they disagree. The design is laid out in how to run a side-by-side email verifier test.
Worked example. A team draws a random 5,000-address sample and runs it through Verifier A and Verifier B on the same morning. The results are illustrative.
| Verifier A | Verifier B | |
|---|---|---|
| Valid | 4,150 (83.0%) | 4,400 (88.0%) |
| Invalid | 450 (9.0%) | 420 (8.4%) |
| Risky / Unknown / Catch-all | 400 (8.0%) | 180 (3.6%) |
Verifier B looks better on paper because it has more Valids and fewer unknowns. Next, the team builds the disagreement set: 300 addresses B calls Valid that A puts in Risky/Unknown. They send to those 300 opted-in contacts from a warmed domain and record 27 hard bounces, 9% of the disputed addresses.
Assume the 4,100 addresses both tools marked Valid bounce at 0.5% (about 21 bounces), and A's remaining 50 Valids that B didn't mark Valid produce 1 bounce:
- Verifier A's Valid bounce rate: (21 + 1) ÷ 4,150 ≈ 0.53%
- Verifier B's Valid bounce rate: (21 + 27) ÷ 4,400 ≈ 1.09%
B's extra 250 net Valids came at the cost of doubling the bounce rate. Whether that trade is acceptable depends on step 1 of the framework. A cold-outreach team protecting domains should choose A. A team for whom the 273 recovered good contacts are worth a 1.09% bounce rate might choose B. Both tools could honestly advertise "99% accuracy" under some formula, which is exactly why you test.
Bottom line: test on your own data, size the sample for the bounce rate you care about, and let real sends settle the disagreements.
Hands-on tutorial: verifying a list for maximum accuracy with Unlimited Verifier
This walkthrough applies the principles above in Unlimited Verifier. Its standard verification is unlimited on every plan, including Free, so re-verifying Unknowns or re-checking a list before a send doesn't cost extra per email. Bulk processing works by exporting from your ESP or CRM, verifying, and re-importing, or by calling the API. There are no native ESP/CRM/Zapier integrations.
- Spot-check first. Paste a few known-good and known-bad addresses into the free single-email checker to see how verdicts are presented.
- Create an account. Sign up for Unlimited Verifier. The Free plan allows 25 lists a month of up to 150 emails each plus 750 deep verifications. Pro ($29/month, or $25/month billed annually) allows unlimited lists of up to 25,000 emails each and 25,000 deep verifications a month.
- Export your list from your ESP or CRM as CSV or Excel. Files can be up to 10MB, and the email column is detected automatically, so you don't need to reformat.
- Split large files so each is within your plan's per-list cap (150 on Free, 25,000 on Pro).
- Upload and verify each list. Every address gets syntax, domain, MX and SMTP mailbox checks plus catch-all, disposable and role-based detection.
- Review the three buckets. Treat Valid as sendable, Invalid as suppress, and Risky as a segment needing a decision.
- Use your deep-verification allowance where uncertainty is highest: Risky addresses and high-value contacts. Unlimited Verifier's stated 99.5% accuracy figure applies to deep verification.
- Re-verify leftovers 24–72 hours later. Greylisting and temporary blocks often clear.
- Export results as CSV, Excel or JSON and download promptly. Results are kept 24 hours on Free and 30 days on Pro.
- Re-import and send in stages. Start with Valids, monitor hard bounces in your first batches, then decide on the Risky segment.
Worked example: cleaning a 60,000-contact list on Pro
A SaaS company has 60,000 trial-signup contacts collected over 18 months.
- Splitting: 60,000 ÷ 25,000 per list = 2.4, so upload 3 files (e.g., 20,000 + 20,000 + 20,000). Pro allows unlimited lists, so the split costs nothing.
- Illustrative results: 48,600 Valid (81%), 7,200 Risky (12%), 4,200 Invalid (7%).
- Deep verification: the 7,200 Risky addresses fit inside the 25,000 monthly allowance, leaving 17,800 deep verifications for the highest-value Valids, such as accounts that converted to paid.
- Cost: at $29/month, verifying 60,000 addresses works out to $29 ÷ 60 ≈ $0.48 per 1,000. Because standard verification is unlimited, verifying a second 60,000-address list the same month brings the effective cost to about $0.24 per 1,000, with no added spend.
- Send plan: mail the 48,600 Valids first in staged batches. If the early bounce rate stays under 1%, continue. Handle Risky addresses as a separate, monitored segment.
For teams that need automation, the email verification API on Pro supports single-email checks and bulk batches of up to 10,000 emails per request, within a 100,000-emails-a-month API allowance.
Bottom line: accuracy in practice comes from workflow (splitting, re-checking Unknowns, using deep verification on the risky slice, sending in stages) as much as from the verifier itself.
Which email verifier is the most accurate?
No verifier is the most accurate on every list. The best tool for you is the one that delivers your target bounce rate with the fewest false invalids on your mix of domains. Head-to-head results depend on test data, which is why which email verifier is the most accurate focuses on how to decide, not just who wins.
For published head-to-head testing, the independent email verifier accuracy benchmark for 2026 sets out its methodology and limitations. The roundup of the best email verifiers ranked by independent tests aggregates third-party results. A credible benchmark discloses test-set size and composition, its ground-truth method, the run date, and both the accuracy and unknown rate for each tool.
Tool comparison: accuracy-relevant differences
The table compares tools on features that affect how accuracy shows up in your results, based on public documentation. It doesn't rank accuracy, because no fair accuracy ranking exists without testing on your data.
| Tool | Result categories (per public docs) | Accuracy-relevant differentiators | Watch out for |
|---|---|---|---|
| Unlimited Verifier | Valid / Risky / Invalid | Unlimited standard verification lets you re-check Unknowns at no extra cost. Open-source engine lets you inspect the logic. States 99.5% accuracy for deep verification | No native ESP/CRM integrations: workflow is CSV export/import or API. Per-list caps (150 Free, 25,000 Pro) mean big lists must be split |
| ZeroBounce | valid, invalid, catch-all, unknown, spamtrap, abuse, do_not_mail | Granular sub-statuses (e.g., abuse, do_not_mail). Offers AI-based scoring aimed at catch-all addresses | More categories means more mapping work in side-by-side tests. Re-verifying consumes credits |
| NeverBounce | valid, invalid, disposable, catchall, unknown | Owned by ZoomInfo. Strong emphasis on native ESP/CRM integrations | Fewer granular risk categories than ZeroBounce. Catch-alls reported as a status, with less scoring detail |
| Kickbox | deliverable, undeliverable, risky, unknown | Sendex™ quality score for each address. Focus on developer API and integrations | Score interpretation requires choosing your own cut-off threshold |
| Bouncer | deliverable, risky, undeliverable, unknown | EU-based with a GDPR-focused positioning. Offers a separate toxicity check | Toxicity data is an add-on signal, not part of core verification accuracy |
For a broader comparison beyond accuracy (features, workflow fit, support), see our guide to the best email verification tools and the full tool-by-tool review.
Why Unlimited Verifier is a strong fit for accuracy-focused teams
The economics of accuracy are often overlooked. Most accuracy gains in practice come from re-checking: re-verifying Unknowns after greylisting clears, re-verifying lists right before a send, and running side-by-side tests. Under per-email credit pricing, every re-check costs money, so teams skip it. With unlimited standard verification, re-checking is free, which makes the accuracy-maximising workflow the default. Add Valid/Risky/Invalid output that keeps ambiguous results out of your sendable pile, plus an open-source engine you can audit, and you have a verifier built around verifiable accuracy rather than a slogan.
How we compared (and limitations)
The comparisons in this guide are based on public documentation from each vendor: category schemes, named features and stated claims. We didn't run our own benchmark for this page, and accuracy figures are presented as vendor claims, not measured results. Category names and features change, so confirm current details on each vendor's site. Unlimited Verifier is our own product. We've limited claims about it to documented plan facts and its stated accuracy figure, and the testing framework above lets you check every claim, ours included.
Bottom line: shortlist on features that matter to you, then pick the winner with a side-by-side test on your own data.
How does accuracy connect to pricing, automation, compliance and ROI?
Accuracy decisions affect cost, workflow and legal exposure. These are the connections to plan for.
Email verification pricing
Pricing models shape how accurate your process can be. Credit-based pricing charges per address checked, which discourages re-verification. Unlimited models remove that penalty. When comparing email verification pricing, calculate cost per 1,000 verified across a realistic month, including re-checks of Unknowns and pre-send re-verification, not just the first pass. The detailed comparison is in our email verification pricing breakdown.
Email verification API and automation
Verifying at the point of capture is the most accurate verification there is, because data is checked before it decays. Real-time checks on signup forms catch typos and disposable addresses immediately. Scheduled batch jobs keep existing lists fresh. See email verification API and automation for the concept and the API and automation implementation guide for patterns like retrying Unknowns asynchronously.
Email verification compliance and hygiene
Verification is a hygiene practice, not a consent mechanism. A Valid address you have no permission to email is still a compliance problem. In the US, the FTC's CAN-SPAM compliance guide sets the rules for commercial email. In the UK, the ICO oversees data protection and electronic marketing rules, and running personal data through a verifier is processing that should be covered by your data agreements. Industry bodies like M3AAWG publish sender best practices that reinforce list hygiene. More in email verification compliance and hygiene and the compliance and hygiene playbook.
Email verification for ecommerce and SaaS
Accuracy priorities differ by business model. Ecommerce lists skew toward consumer webmail, where verifiers perform best, so the main risks are typos at checkout and disposable addresses used to grab discount codes. SaaS lists mix personal and work addresses, with more catch-alls and Microsoft 365 tenants and a higher cost for false invalids on paying users. See email verification for ecommerce and SaaS and the sector-specific guide.
Email deliverability and ROI
Accurate verification protects the reputation that determines inbox placement, and inbox placement drives revenue. The value of a percentage point of accuracy is easiest to see in money terms: fewer bounces protect the sending domain, and fewer false invalids keep real buyers on the list. The email marketing ROI guide shows how to put numbers on both sides. If you're starting from scratch, the introduction to email verification covers the fundamentals.
Bottom line: the most accurate verifier on paper underperforms if pricing discourages re-checks or verification happens long before the send.
Common mistakes that make verification less accurate
- Trusting the headline accuracy number. Without the formula and the unknown rate, "99%" is unverifiable. Ask for both.
- Treating catch-all as Valid. This is the single biggest source of post-verification bounces. Segment and stage catch-alls.
- Treating role-based as Invalid.
sales@andsupport@addresses are often real and responsive. Suppressing them blindly creates false invalids. - Verifying too early. Verifying in January and sending in April lets months of decay through. Verify close to the send.
- Never re-checking Unknowns. Many resolve after 24–72 hours. Abandoning them wastes contacts or sends risk through untested.
- Testing with tiny samples. 200 addresses can't measure a sub-1% bounce rate. Use the sample-size math above.
- Testing tools on different days. Results drift, and same-day runs are the only fair comparison.
- Comparing raw category counts. More Valids doesn't mean more accurate. Settle the disagreements with real sends.
- Assuming Valid means inbox. Authentication, reputation and content still decide placement. Follow Google's sender guidelines regardless of verification results.
- Letting results expire unused. On Unlimited Verifier's Free plan, results are kept 24 hours. Export immediately after verification.
Bottom line: most accuracy problems come from process (timing, segmentation, sample size), not from the verifier, and all of them are fixable.
Putting it together
Email verifier accuracy isn't one number. It combines a false-valid rate, a false-invalid rate and a coverage rate, all measured on a specific list at a specific time. The tools worth trusting are open about all three, and the teams that get the best results verify close to the send, segment catch-alls and Unknowns, re-check what's ambiguous, and confirm with real bounce data.
You can apply all of this today. Run your own seed list through the checker, size a real sample with the formula above, and measure the bounce rate that actually matters. If you want a verifier whose economics reward that re-checking discipline, Unlimited Verifier's unlimited standard verification, Valid/Risky/Invalid output and open-source engine are built for exactly this workflow.
Three ways vendors calculate accuracy
| Formula | What it counts | Why it can mislead |
|---|---|---|
| Decisive accuracy = correct Valid + correct Invalid ÷ all Valid + Invalid verdicts | Only addresses the tool committed to | Inflates when hard cases are pushed into Unknown/Risky |
| Overall accuracy = correct verdicts ÷ all addresses tested | Treats Unknown as not correct | Honest, but rarely published |
| Bounce-based accuracy = 1 − (bounces among Valid ÷ total Valid) | Only the false-valid side | Ignores good addresses wrongly marked Invalid |
Frequently asked questions
Are email verifiers 100% accurate?
No. No email verifier can be 100% accurate. Catch-all domains, greylisting, some Microsoft 365 tenants and mailboxes that change status over time make some verdicts impossible to confirm without sending a real message. Reputable tools usually land around 95–99% on decisive results. Any vendor promising zero bounces is overstating what SMTP-based verification can do, so plan for a small residual bounce rate.
Why do two email verifiers give different results for the same address?
Different verifiers use different methods, IP reputations, timeouts and retry logic. A server may greylist one tool and answer another normally, or rate-limit a verifier with a poor IP reputation. Vendors also differ in how they classify catch-all and ambiguous responses. One tool might say Risky where another says Valid. Comparing their disagreements against real send results shows which tool is more reliable for your data.
What is a good bounce rate after email verification?
A good hard bounce rate after verification is under 1%. Many deliverability practitioners treat 2% as the upper limit before sender reputation starts to suffer. If your post-verification bounces exceed that, check whether you sent to Risky or catch-all addresses, whether the list aged after you verified it, or whether the verifier is misclassifying addresses on your main domains.
How do catch-all domains affect verifier accuracy?
Catch-all domains accept mail for any address at the SMTP stage, so a verifier cannot confirm whether a specific mailbox exists. Most tools label these Accept-All or Risky rather than Valid or Invalid. Some advanced verifiers use extra signals to resolve a portion of them, but none can do this reliably for every case. Catch-alls are the largest source of uncertainty in verification results.
How often should I re-verify my email list?
Re-verify any list that hasn't been mailed in about three months, and always before a large campaign. Email data decays continuously as people change jobs and providers close or recycle mailboxes, so a list that verified clean months ago will degrade. Verifying at the point of capture with real-time API checks, plus periodic bulk cleaning, keeps accuracy high.
Does email verification send an email to the address?
No. Standard email verification does not send a message. It checks syntax, confirms the domain and MX records, and opens an SMTP conversation with the mail server to ask whether the mailbox exists. It disconnects before any message is delivered. That is why some verdicts stay uncertain: the only definitive test is an actual send.
Should I send to addresses marked Unknown or Risky?
Treat Unknown and Risky addresses with caution. Send to them separately, in small batches, from a warmed-up sending domain, and watch the bounces. Remove anything that hard-bounces. For high-value campaigns or a fragile sender reputation, many senders exclude them entirely. Your decision should depend on how valuable those contacts are compared with the deliverability risk.
Can a verifier mark a valid email as invalid?
Yes. A false negative happens when a real, working address is labelled Invalid, often because of a temporary server error, greylisting or aggressive anti-verification defences. Bounce-based accuracy figures ignore this error entirely, so a tool can look accurate while silently discarding good contacts. Spot-check a sample of Invalid results, especially on important domains, before deleting them.
Is free email verification as accurate as paid tools?
Usually not for bulk use. Free checkers often perform only syntax and DNS checks, or limited SMTP checks from shared IPs that mail servers throttle. That produces more Unknown results and more errors. Paid verifiers generally invest in IP reputation, retry logic, catch-all handling and greylisting management. Free tools work for one-off checks, but test before relying on them for lists.
How do I test an email verifier's accuracy myself?
Build a seed list of addresses you know are valid and invalid. Then run it, plus a real sample of your own data, through each candidate tool. Record the decisive accuracy and the unknown/risky rate for each. Send to the addresses where the tools disagree and check the bounces. Pick the tool with the best mix of correct verdicts and low unknowns.
Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification
Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.
| Free | Pro | |
|---|---|---|
| Price | $0 | $29/month ($25/month billed annually) |
| Lists | 25 a month, up to 150 emails each | Unlimited, up to 25,000 emails each |
| Deep verifications | 750 a month | 25,000 a month |
| API access | No | Yes (100,000 emails a month) |
| Result retention | 24 hours | 30 days |
Why teams choose Unlimited Verifier
- Unlimited standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
Unlimited Verifier states 99.5% accuracy for deep verification.
Create a free account and verify your next list before you hit send.
Want to test a single address first? Try the free email checker.