Article
Why ZeroBounce and NeverBounce Disagree on the Same Email
By Unlimited Verifier Team ·

Summary
ZeroBounce and NeverBounce disagree on the same email because their status labels differ, their SMTP probes run from different infrastructure at different times, and they resolve inconclusive answers like catch-all domains and timeouts by different rules. Most gaps are classification differences rather than contradictory verdicts on whether a mailbox exists.ZeroBounce and NeverBounce disagree on the same email because they label results with different category rules, probe the recipient's mail server at different times and from different infrastructure, and settle uncertain answers, such as catch-all domains and timeouts, by different policies. In a side-by-side comparison, many of the gaps are classification differences rather than contradictory verdicts on whether the mailbox exists.
This article is part of our guide to email verifier accuracy.
Quick answer
- Labels differ. A "catch-all" in one tool can be "valid" or "unknown" in the other, because each vendor maps its own statuses onto the same underlying server response.
- Probes differ. Each tool connects from its own addresses, at its own time, with its own retry logic. A mailbox server can answer each one differently.
- Uncertainty is settled differently. Greylisting, timeouts and catch-all domains leave a single SMTP check inconclusive, and each vendor decides how to resolve that.
- Measure before you trust. Cross-tabulate both outputs, treat hard conflicts as Risky until resolved, and use your own bounce data as the tiebreaker.
Why do ZeroBounce and NeverBounce disagree on the same email?
Four mechanisms cause most disagreements, and each can produce a different verdict on the same address.
- Different taxonomies. Each vendor defines its own status list, so the same underlying fact can receive a different label.
- Different probes. An SMTP check is a live exchange with a remote server. The answer depends on the sending connection, the timing, and how that server treats it.
- Different uncertainty rules. When the server gives an ambiguous answer, one vendor may return "unknown" while another retries and reaches a verdict.
- Different timing and caching. A mailbox can be created, filled or deleted between two checks. A vendor that caches results reports an earlier answer, while one that re-probes reports the current one.
None of these means one vendor is lying. They mean a single SMTP check is weaker evidence than a single label suggests.
Bottom line: A disagreement usually means the two tools answered different questions, or answered the same question with different confidence.
Do ZeroBounce and NeverBounce mean the same thing by "valid"?
No. Their status lists overlap but do not match, so "valid" in one tool does not carry the same meaning as "valid" in the other.
The table below reflects how each vendor describes its statuses in public documentation at the time of writing. Labels change, so check current docs before you build a mapping.
| Situation | ZeroBounce (as publicly described) | NeverBounce (as publicly described) | Practical handling |
|---|---|---|---|
| Server accepts the mailbox | Valid | valid | Send, but watch hard bounces |
| Domain accepts every address | Catch-all | catchall | Treat as Risky; the mailbox is unconfirmed |
| Disposable address | Grouped under Do Not Mail, with a sub-reason | disposable | Remove from B2B sends |
| Role address such as info@ | Grouped under Do Not Mail, with a sub-reason | Reported through a role indicator rather than a headline status | Hold back from personal outreach |
| No conclusive answer | Unknown | unknown | Re-run; never treat as valid |
| Spamtrap or abuse indicator | Separate Spamtrap and Abuse statuses | No equivalent top-level status listed | Use as a signal, not proof |
The spamtrap row matters most. Spamtrap and abuse signals depend on each vendor's own data sources, and a single SMTP check cannot confirm them. When one tool flags a spamtrap and the other does not, the gap usually reflects data coverage, not a different reply from the mailbox server.
Bottom line: Compare category by category, not headline by headline. A "valid" with a role flag is not the same as a clean valid.
How does an SMTP check produce different answers?
An SMTP check asks the recipient's mail server whether it would accept mail for an address, usually by issuing RCPT TO during a session and reading the reply code. Under RFC 5321, a 2xx reply means the recipient is accepted, a 5xx reply is a permanent rejection, and a 4xx reply is a temporary failure the sender should retry. RFC 3463 defines the enhanced status codes, such as 5.1.1 for a bad destination mailbox.
The disagreements come from what happens between those replies:
- Greylisting and deferral. Greylisting, a common anti-spam technique, answers a first-time sender with a temporary 4xx and accepts the message on a later attempt. A tool that retries gets a 250. A tool that gives up after one attempt records an unknown.
- Throttling. Large providers commonly slow or defer connections that look like automated probing. Two tools probing from different IP reputations can receive different treatment.
- Non-committal responses. Some servers accept the connection without revealing whether a specific mailbox exists. That reply cannot be read as a verdict in either direction.
- Probe identity. The sending domain and envelope sender a tool uses can influence how a server responds, and each vendor uses its own.
The practical implication is that an SMTP check is a question put to a server that is free to answer selectively. Two honest tools asking at different times can get different answers without either one making an error.
Bottom line: The mailbox server is the source of the answer, but how the question is asked, and how often it is retried, shapes what comes back.
Why does catch-all handling cause most of the mismatch?
Catch-all domains are usually the largest source of disagreement, because the server accepts every address. A successful reply therefore says nothing about the specific mailbox.
To detect a catch-all, a verifier typically probes a random, made-up address at the same domain. If that address is accepted, the domain is catch-all and the real address cannot be confirmed. The tool must then choose a policy: label the address valid, label it catch-all, or route it to a Risky bucket.
Each vendor makes that choice differently. One may label every accepted address on a catch-all domain as catch-all. The other may report it as valid when it has no reason to expect a bounce. Neither is measuring the mailbox. Both are applying a policy.
So "valid on a catch-all domain" is best read as a guess with a label attached. Unlimited Verifier detects catch-all domains and sorts their addresses into its Risky bucket rather than Valid. You can read more on how accurate email verifiers are on catch-all domains, and check a batch with catch-all email verification.
Bottom line: On a catch-all domain, a disagreement is usually about policy, not evidence. Hold those addresses in their own segment.
Can the same verifier disagree with itself?
Yes. Re-running a check on the same address can return a different result, because the server's answer depends on timing, connection history and the mailbox's current state. This is the most common reason a "fix" fails: the second run may flip the result rather than settle it.
Some practical rules follow from that:
- Don't loop. Rapid repeated probes from one connection can trigger throttling and produce more unknowns, not fewer.
- Wait before re-checking. Re-run hard conflicts after a pause. A day or more is a reasonable starting point; this is a practitioner judgment, not a vendor rule.
- Keep the history. Record each run's date and result. If an address flips between runs, treat it as Risky until it stabilises.
Bottom line: A single result is a snapshot. Two consistent results across a pause are much stronger evidence.
Which kind of disagreement are you looking at?
Most disagreements fall into a few types, and each calls for a different response.
| Disagreement | Most likely cause | Action |
|---|---|---|
| Valid vs Invalid (hard conflict) | One probe received a 5xx while the other received a 250, or the mailbox changed between checks | Re-verify after a pause; hold as Risky until resolved |
| Valid vs Catch-all | Domain-level policy, not mailbox evidence | Move both to Risky; send only in a small test |
| Valid vs Unknown | Timeout, deferral or greylisting | Re-run after a delay; never count an unknown as valid |
| Catch-all vs Invalid | Unusual; the domain's mail setup may have changed | Re-run; check the domain and its MX records |
| Unknown vs anything | Inconclusive on one side | Hold back until a second check resolves it |
If many addresses return unknown, the tool may be struggling with a particular set of servers. Check what a good unknown rate for an email verifier looks like before accepting high unknown counts as normal.
The hard conflicts deserve the closest attention. A "valid" label that bounces in your campaign is a false positive, which is explained in what a false positive is in email verification.
Bottom line: Sort disagreements by type first. Most of them need a hold, not a verdict.
How do you tell which verifier is right for your list?
You cannot settle this from vendor claims. Vendor accuracy figures are generally measured on different test sets and definitions, so they are rarely directly comparable. Read whether vendor accuracy claims for email verifiers are trustworthy before relying on any headline number.
Use your own list as the test:
- Run the same file through both tools on the same day, so you compare near-simultaneous probes.
- Join the results on the email address and build the four-by-four matrix of labels.
- Split disagreements by type using the table above.
- Look for clustering by domain. If hard conflicts concentrate on a few providers, the cause is often probing behaviour at those servers. Consumer mailbox providers behave differently from each other, which is why accuracy on Gmail versus Outlook addresses is worth checking separately.
- Send a small, controlled test to a sample of the hard conflicts, and record hard bounces, delays and complaints.
- Score each tool on outcomes. The tool whose "valid" predicts fewer hard bounces on your list is the better fit for your data, even if its headline accuracy is lower.
- Repeat quarterly. Mailbox availability and provider behaviour change, so one comparison goes stale.
For broader selection criteria, see how to choose an email verifier and the best email verification tools.
Bottom line: Your own bounce outcomes, not a vendor's accuracy claim, are the ground truth for your list.
Do you need two verifiers, or is one enough?
For most lists, one verifier used consistently is enough, provided you know its limits. A second opinion earns its cost in a narrower set of cases.
The reason is asymmetric. Wrongly removing a real address costs you a contact. Wrongly sending to a dead or risky address can cost you sender reputation. So a second opinion is most valuable on addresses your first tool marks Valid or Catch-all, where a wrong label leads to a send. It is less valuable on addresses marked Invalid, where removal is the safe default.
In practice, a two-tool check is worth running when:
- You are about to send to a large segment that will be hard to recover from if it bounces.
- Your list is mostly catch-all domains or unknowns, so one tool's policy drives most of the outcome.
- You are preparing evidence for a compliance review, where you need to show how decisions were made.
Keep the second check limited to the rows that matter. For ongoing collection, real-time email validation at the point of entry keeps the problem from growing in the first place.
Bottom line: Spend the second opinion where a wrong label leads to a send, not on every address.
Hands-on tutorial: compare two verifier outputs in a spreadsheet
This tutorial assumes you have exported results from two tools. Any spreadsheet program works.
- Export both result files as CSV. Keep the originals unchanged so you can re-check them later.
- Standardise the email column. Trim spaces and lowercase both files. Email addresses are almost always matched case-insensitively in practice, and a clean key prevents false mismatches.
- Build one lookup. Place the first tool's results in one sheet and the second tool's in another. In a third sheet, use
XLOOKUPorVLOOKUPto pull the second tool's label beside each address. - Create a crosstab. Insert a pivot table with the first tool's label as rows and the second tool's as columns. Use the count of addresses as the value.
- Check the totals. Each row total should match the first tool's count for that label, and each column total should match the second's. If they don't, you have duplicates or missing addresses.
- Isolate the hard conflicts. Filter for Valid vs Invalid in either direction. These rows need a third opinion.
- Get a third opinion on those rows only. If you do not have an account yet, sign up first. The Free plan allows lists of up to 150 emails, so split a larger conflict file into chunks of 150. Pro allows lists of up to 25,000 emails. Then upload and verify a list. The tool sorts each address into Valid, Risky or Invalid and flags disposable and role-based addresses. For a handful of addresses, the free email checker is quicker. Treat the third result as a tiebreaker, not ground truth.
- Export before the retention window closes. Results are kept for 24 hours on Free and 30 days on Pro, so save your files immediately.
If you want to script the same workflow, the email verification API is available on Pro. It supports single-email checks and bulk batches of up to 10,000 emails per request, within the plan's 100,000-email monthly API allowance. For the wider workflow options, see email verification API and automation.
Bottom line: A crosstab turns two conflicting files into a short, specific list of rows that need a decision.
Worked example: reconciling a 20,000-row list
The figures below are hypothetical and illustrate the method. "Tool A" and "Tool B" stand in for the two vendors.
Setup: A B2B SaaS company has 20,000 contacts from a trade-show import and an older CRM. Both tools return four labels: Valid, Catch-all, Invalid and Unknown. (For more on this kind of list, see email verification for ecommerce and SaaS.)
Crosstab (rows: Tool A, columns: Tool B):
| Tool A ↓ / Tool B → | Valid | Catch-all | Invalid | Unknown | Row total |
|---|---|---|---|---|---|
| Valid | 15,300 | 700 | 200 | 200 | 16,400 |
| Catch-all | 400 | 1,200 | 100 | 200 | 1,900 |
| Invalid | 100 | 300 | 900 | 0 | 1,300 |
| Unknown | 100 | 100 | 100 | 100 | 400 |
| Column total | 15,900 | 2,300 | 1,300 | 500 | 20,000 |
Analysis:
- Agreement: 15,300 + 1,200 + 900 + 100 = 17,500 rows (87.5%).
- Disagreement: 20,000 − 17,500 = 2,500 rows (12.5%).
- Split of the 2,500:
- Valid vs Invalid (hard conflict): 200 + 100 = 300 rows (1.5%)
- Valid vs Catch-all: 700 + 400 = 1,100 rows (5.5%)
- Catch-all vs Invalid: 100 + 300 = 400 rows (2.0%)
- Involving Unknown: 200 + 200 + 0 + 300 = 700 rows (3.5%)
- Check: 300 + 1,100 + 400 + 700 = 2,500 ✓
Most of the disagreement is classification, not contradiction. Only 300 rows directly conflict on Valid versus Invalid.
Sending rule: Under a conservative rule, you send only where both tools say Valid. That is 15,300 contacts (76.5%). The remaining 4,700 are held back.
Tiebreaker scope: The 300 hard conflicts are the priority. The 1,100 Valid-vs-Catch-all rows are a policy question and can go to a small test send instead.
Plan fit and cost:
- List size: 20,000 rows fit in one Pro list, since Pro allows lists of up to 25,000 emails.
- Deep verifications: Pro includes 25,000 deep verifications a month. The 300 hard conflicts use 300 of them, or 1.2% of the allowance. Even the full 2,500 disagreement rows use only 10%.
- Free-plan check: Free allows 25 lists a month of up to 150 emails each, so 3,750 emails in total. Covering 20,000 rows would need 20,000 ÷ 150 = 133.3, or 134 lists, which exceeds the monthly limit. Free cannot cover this file in one month.
- Cost: One Pro month is $29, or $25 a month billed annually. At full use of the 25,000 deep allowance, that works out to $29 ÷ 25 = $1.16 per 1,000 deep verifications, or $1.00 billed annually. Compare email verification pricing across vendors using the same list size and the same unit.
Bottom line: In this example, a 12.5% gap between two tools reduces to 300 hard conflicts that need attention, and 15,300 contacts that are safe to send to.
What sending rule should you use when verifiers disagree?
Use a conservative rule: send only to addresses that every verifier you trust labels Valid, and hold everything else in labelled segments.
The reasoning is about the cost of error. A hard bounce to an address that looked valid adds to your bounce rate. Mailbox providers such as Google publish sender requirements that make list hygiene part of the reputation picture. Holding back a few thousand addresses for a week usually costs far less than a damaged sender reputation. For a view of what a valid result does and does not promise, see whether a valid result means the email will be delivered.
Keep the held segments separate:
- Hard conflicts: Re-verify after a pause, then decide based on a controlled send.
- Catch-all: Test in small batches and watch hard bounces on each.
- Unknown: Re-run after a delay; do not send until resolved.
If you need a defensible policy, write down the rule, the tools used, and the re-check cadence before the list goes out. The email verification compliance and hygiene process is easier to defend when the rule was set in advance. For ongoing upkeep, email list maintenance best practices covers scheduling.
Bottom line: Send only where the evidence agrees, and treat every other segment as a test, not a list.
Common mistakes
- Treating one tool as ground truth. Neither vendor's label is final until your bounce data confirms it.
- Averaging labels. Scoring Valid as 1 and Invalid as 0, then averaging, hides the hard conflicts you most need to see.
- Re-running in a loop. Repeated probes from one connection can trigger throttling and create more unknowns.
- Comparing headline accuracy as if it measured the same thing. Test sets and definitions differ, so the numbers are not like-for-like.
- Counting unknowns as valid. An inconclusive result is not a clean one.
- Comparing prices per credit. Credit packs and per-email rates differ. Convert both to cost per 1,000 verified emails, using the same list size.
- Ignoring data age. A list verified last quarter may have changed, so some disagreement can reflect timing rather than the tools.
- Losing your results. Free keeps results for 24 hours and Pro for 30 days. Export before they expire, because you will need them for your audit trail.
Bottom line: Most errors come from trusting a single label, or from treating an inconclusive result as a verdict.
How we compared (and limitations)
This article is based on public documentation: RFC 5321 for SMTP reply classes, RFC 3463 for enhanced status codes, the status lists ZeroBounce and NeverBounce describe publicly, and Unlimited Verifier's published plan details. We have not run controlled tests of either vendor's service, and vendor labels can change, so check each vendor's current documentation before you build a mapping.
The worked example uses hypothetical figures to show the method. The percentages and counts are not measurements of any real tool.
Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark. For the wider context, see the independent email verifier accuracy benchmark for 2026, how accurate email verification really is, and whether email verifiers really have 99% accuracy. For a deeper explanation of why tools disagree in general, read why different email verifiers give different results.
Bottom line: Use this article to understand the mechanisms and design your own comparison, then let your own bounce data decide.
Conflict resolution rules
| Pair of results | Classification | Action |
|---|---|---|
| Valid vs Valid | Agreement | Send |
| Catch-all vs Valid | Classification difference | Treat as Risky |
| Unknown vs Valid | Uncertainty difference | Re-run before sending |
| Valid vs Invalid | Hard conflict | Hold as Risky, check bounce history |
Frequently asked questions
Is one email verifier more accurate than the other?
Neither is universally more accurate. Accuracy depends on the mail servers in your list, the statuses you act on, and how each tool handles catch-all and greylisted domains. Test both on a sample of addresses with known outcomes from your own bounce data to find out which fits your list.
What does a catch-all status mean?
A catch-all status means the domain accepts mail for any address, so the server gives a positive answer even for mailboxes that do not exist. The individual mailbox is therefore unconfirmed. Treat catch-all addresses as risky rather than fully valid, especially for cold outreach.
Why does an email show valid in one tool and unknown in the other?
The two tools reached different conclusions from the same server behavior. One may have received a timeout or greylisting response and returned unknown, while the other retried and received a clear accept. Each vendor's retry and uncertainty rules decide the final label.
Can greylisting cause verifier disagreements?
Yes. Greylisting makes a server temporarily reject first-time connections and expect a retry later. A verifier that retries after a delay may get a definitive answer, while one that does not retry may return an inconclusive result.
Should I remove emails when the two tools disagree?
Not automatically. Treat hard conflicts, such as valid against invalid, as risky until you resolve them. Send only to the subset you are confident in, and use your own hard bounce history to decide the rest.
How do I compare ZeroBounce and NeverBounce results?
Run the same list through both, export each result, and build a cross-tab of their statuses. Group the pairs into agreement, classification difference, and hard conflict. Then check a sample of each group against real delivery outcomes to see which tool's labels match reality for your audience.
Why do results change when I re-verify the same list?
Mailboxes are created, filled, or deleted over time, and mail servers change their policies. A verifier that caches results reports an earlier answer, while one that re-probes reports the current state. Re-verification can therefore shift results even with the same tool.
Do disposable and role addresses get handled the same way?
Not always. Vendors group and label disposable and role addresses differently, and one may flag a role address through an indicator rather than a headline status. Check each tool's current documentation and map the categories before building suppression rules.
Do verifier disagreements mean one tool is wrong?
Usually not. Disagreements most often mean the tools answered different questions or answered the same question with different confidence. A single SMTP check is weaker evidence than its label suggests, so treat any single verdict as a probability rather than a fact.
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.