Article
Is NeverBounce Accurate? What Its Results Really Mean for Your Bounce Rate
By Unlimited Verifier Team ·

Summary
NeverBounce is reliable at flagging dead addresses, but its "valid" label is a prediction rather than a delivery guarantee. Its accuracy drops on catch-all, disposable and unknown addresses. Measure the false-valid rate on your own list, since vendor accuracy claims come from the vendor's own test data.NeverBounce is accurate at flagging dead addresses, but its "valid" label is a prediction, not a delivery guarantee, and its reliability drops on catch-all and unknown addresses. Its labels come from SMTP checks that some mail servers answer clearly and others don't, so the question that matters is how often its "valid" results bounce on your own list. This guide explains what accuracy means for a verifier, where NeverBounce's checks have blind spots, and how to measure its results yourself.
Quick answer
- Most dependable on dead addresses. Syntax errors, missing domains and rejected mailboxes give the clearest evidence, so the "invalid" label is the one to trust most.
- The costly error is a false "valid." A dead address marked valid bounces and harms your sender reputation. A real address marked invalid only costs you a contact.
- Vendor accuracy figures describe the vendor's own test data. They don't predict your bounce rate, so measure on a sample of your list.
- Plan around two numbers: keep bounces on the "valid" segment under 1% and total bounces under 2%.
- Treat catch-all, disposable and unknown results as risky, not as safe.
Verification is a prediction, not a delivery test. NeverBounce checks the syntax and domain of an address, then asks the receiving server whether it will accept the mailbox. Servers that answer clearly produce reliable labels. Servers that accept everything, or refuse to answer, do not.
Bottom line: NeverBounce is a good predictor of dead addresses. Its "valid" label is a probability, and you should test that probability on your own data.
What does "accurate" mean for an email verifier?
A verifier can be wrong in two directions, and the two errors have very different costs. A false valid means the tool says the address is deliverable but the message bounces. A false invalid means the tool says the address is dead but the mailbox was real.
A false valid damages you directly. Bounces feed into the bounce rate your ESP monitors, and mailbox providers read that rate as a signal about your list. A false invalid costs reach and revenue, but it doesn't hurt deliverability.
The metric to track is the false-valid rate:
False-valid rate = valid-labelled addresses that bounce ÷ valid-labelled addresses you sent to
This matters more than a headline accuracy percentage, because it measures the error that reaches the inbox and the ESP's review queue.
Bottom line: Judge any verifier by its false-valid rate, since that is the error that triggers bounce spikes and account reviews.
What accuracy does NeverBounce claim?
NeverBounce describes its accuracy and deliverability on its website. These are vendor claims, and this guide hasn't independently audited them, so we don't quote a percentage as fact. Check the current page for the figure and the method behind it.
When you read any vendor claim, ask three questions:
- What was the test set? A vendor chooses its own sample, which may differ from your list in domain mix, list age and engagement.
- What counted as correct? A result that matches a mailbox check is different from one that matches an actual delivery.
- Was it measured against bounces? Accuracy against the verifier's own labels is not the same as accuracy against what mail servers did.
Use vendor claims as a starting hypothesis, then test them with the method described later in this guide.
Bottom line: A published accuracy figure is the vendor's statement about its own data. Confirm it against your list before relying on it.
How does NeverBounce decide whether an address is valid?
NeverBounce runs a layered check. It confirms the address has valid syntax, looks up the domain's mail records, then opens an SMTP conversation with the receiving server and asks whether it would accept the recipient. No message is delivered. The SMTP protocol is defined in RFC 5321, and the enhanced status codes that servers return, such as 5.1.1 for a bad mailbox, are defined in RFC 3463.
NeverBounce's public materials describe its result labels. The table below explains what each usually means and what to do with it:
| Label | What it usually means | Practical action |
|---|---|---|
| valid | Syntax and domain check out, and the server accepted the recipient at check time | Eligible to send; start with recently engaged contacts |
| invalid | Bad syntax, no mail server, or the mailbox was rejected | Suppress permanently |
| disposable | A throwaway or temporary-inbox provider | Suppress for most B2B and transactional mail |
| catch-all | The server accepts any recipient, so the mailbox can't be confirmed | Risky; send last and at low volume |
| unknown | No clear answer, such as a timeout, throttling or refusal | Risky; re-verify later |
Each label is a snapshot of one conversation with one server at one moment. A "valid" result from three months ago is not a guarantee today, and mailbox providers change how they respond to verification probes.
Bottom line: Only "invalid" is close to a firm verdict. The other labels are signals that need a sending decision.
Where does NeverBounce's accuracy break down?
Most errors that matter come from a small set of situations. Knowing them lets you plan around them.
| Scenario | What the verifier sees | Real risk | Fix |
|---|---|---|---|
| Catch-all domains (many corporate domains, including some on Microsoft 365) | The server accepts any recipient | A closed or fake mailbox looks identical to a live one, and the bounce can arrive after the message is accepted | Test last and at low volume; monitor bounce reports |
| Throttling or greylisting | No clear reply, or a temporary error | Addresses land in "unknown" rather than valid or invalid | Treat as risky; re-verify after a delay |
| Mailboxes closed after checking | Active at check time | A person leaves between verification and sending | Verify shortly before major sends |
| Spam traps | Look like ordinary active mailboxes | A single SMTP check generally can't tell a trap from a real inbox, so a clean result doesn't rule one out | Suppress long-dormant addresses; enforce a sunset policy |
| Role and disposable addresses | Flagged as a category | Some are real (info@ often routes to a team) |
Decide per segment, not by blanket rule |
Catch-all results deserve the most attention because they are common. On a corporate-heavy list, a large share of addresses can come back catch-all. These are the addresses where a "valid" feeling is least justified, because the server's answer tells you nothing about the individual mailbox.
Bottom line: Catch-all, unknown and trap-prone addresses are where accuracy claims stop meaning much. Build your sending plan around them.
How do you measure NeverBounce's accuracy on your own list?
The most reliable test is a sample-and-send experiment. Verify a representative sample, cross-check it with a second verifier, then send a small controlled batch and log bounces by label.
Here is a worked example with illustrative numbers.
Step 1: Build a 1,000-address sample that mirrors your list: 40% engaged in the last 90 days, 40% dormant for 6–12 months, and 20% with a previous bounce.
Step 2: Verify all 1,000 with NeverBounce. Suppose the labels are:
- Valid: 620
- Catch-all: 110
- Invalid: 180
- Disposable or unknown: 90
Step 3: Send a controlled test to each risky-to-valid segment.
- Valid (620 sent): 5 hard bounces. False-valid rate = 5 ÷ 620 = 0.8%.
- Catch-all (110 sent as a separate test): 9 bounces. Bounce rate = 9 ÷ 110 = 8.2%.
- Invalid (180) and disposable or unknown (90): not mailed. Instead, run them through a second verifier and review disagreements by domain type and SMTP response.
Five bounces is a small count. Using the standard Wilson method, 5 out of 620 gives a 95% confidence interval of roughly 0.3% to 1.9% (our calculation). That's why you should repeat the test with a larger sample before setting a firm policy. The direction of the result is still useful: the valid segment is usable, and catch-all addresses carry most of the risk.
Note the limit of this design. Mailing the invalid segment to measure false invalids would send to addresses you already believe are dead, so you estimate that error from the second verifier's results and a manual sample instead.
Bottom line: A few hundred controlled sends will tell you more about NeverBounce on your list than any published percentage.
What bounce rate should you target after cleaning?
Use two numbers: under 1% on the valid segment, and under 2% total. Sources disagree on the exact ceiling, so here is why we recommend these.
Amazon SES's documentation describes a 5% bounce rate as the level that puts an account under review. Many ESPs act earlier, especially on a single campaign to an unproven list. Google separately advises bulk senders to keep user-reported spam below 0.3% in its sender guidelines, which is a complaint metric, not a bounce metric, but it sits alongside bounces in provider reviews.
Our recommended numbers leave headroom under those triggers. On a 50,000-address valid segment, a 1% false-valid rate means about 500 bounces. A 0.5% rate means about 250. Those gaps matter when a single campaign can cross a threshold.
Bottom line: Plan for under 2% total and under 1% on the valid segment, because most platform triggers act before 5%.
NeverBounce vs Unlimited Verifier: how do they compare?
If you're still shortlisting, the email verifier alternatives pillar covers the wider market, and our best email verification tools guide ranks options by use case. For a direct comparison, the table below uses NeverBounce's public documentation and Unlimited Verifier's published plan facts.
| Feature | NeverBounce | Unlimited Verifier |
|---|---|---|
| Result categories | valid, invalid, disposable, catch-all, unknown | Valid, Risky, Invalid; catch-all, disposable and role-based addresses flagged |
| Pricing model | Check its pricing page for current credit and plan rates | Email verification pricing is flat: unlimited standard verification on every plan, including Free |
| Free tier | Check current terms on its site | 25 lists a month of up to 150 emails each, plus 750 deep verifications; no API access |
| Paid tier | Check its site | Pro at $29/month, or $25/month billed annually: lists up to 25,000 emails, 25,000 deep verifications, API access (100,000 emails a month) |
| Upload | Bulk upload available | CSV or Excel up to 10MB, email column detected automatically |
| Export | Check its documentation | CSV, Excel or JSON |
| API | Available | REST API with API keys; single checks and batches of up to 10,000 emails per request |
| Native integrations | Check its site for supported platforms | No native ESP, CRM or Zapier integrations; use export-and-reimport or the API |
| Results retention | Check its documentation | 24 hours on Free, 30 days on Pro |
| Engine transparency | Not published as open source in its public materials | Open-source verification engine on GitHub |
Where NeverBounce is stronger: if your platform has a documented NeverBounce connector, you skip manual export and re-import. That matters if you verify constantly inside one tool.
Where Unlimited Verifier is stronger: standard verification is flat, so a second opinion on the same list adds no per-email cost. Its three buckets map directly to sending decisions, and its open-source engine lets technical teams read the logic.
For head-to-head detail, see our MillionVerifier vs NeverBounce comparison.
Bottom line: NeverBounce is stronger where a native connector saves work. Unlimited Verifier is stronger on flat standard-verification pricing, a three-bucket structure and inspectable code.
How do you run a two-verifier accuracy check?
This process uses a second verifier to find disagreements, which show you where both tools are uncertain. Unlimited Verifier works well as the second opinion, but any second verifier with a clear label set will do. If you're shortlisting, the guides to ZeroBounce alternatives, Emailable alternatives and EmaiListVerify alternatives cover other options.
- Export your contacts from your ESP as a CSV. Include the email column and a last-engagement date.
- Build a 1,000-row sample that mirrors your list. Engaged, dormant and previously bounced contacts should appear in roughly the same proportions as your full database. A random sort in a spreadsheet works.
- Sign up for the Free plan. It allows 25 lists a month of up to 150 emails each. A 1,000-row sample needs 7 files (six of 150 and one of 100), using 7 of your 25 lists.
- Split the sample into those 7 files and name them clearly, such as
sample_part1.csv. - Upload and verify a list. The email column is detected automatically. Verification checks syntax, domain, MX records and the SMTP mailbox.
- Download results the same day. Free-plan results are kept for 24 hours.
- Build a cross-tab. Join your Unlimited Verifier results to your NeverBounce labels on the email address using a lookup formula. You now have a grid such as NeverBounce "valid" against Unlimited Verifier "Risky".
- Investigate disagreements. For catch-all cases, read the catch-all email verification guidance. For individual high-value addresses, a free email checker spot check is quick.
- Send a controlled test only to addresses both tools label valid. Log hard bounces and their SMTP codes, then calculate the false-valid rate.
Bottom line: Two verifiers plus one controlled send show you where each tool is trustworthy and where neither is.
What does a 40,000-contact cleanup cost?
Pricing depends on your row count, your plan limits and how often you re-verify. Here is the arithmetic for a B2B company with 40,000 contacts considering the Pro plan.
- List split: Pro allows lists of up to 25,000 emails each. For 40,000 contacts, upload two files: 25,000 + 15,000.
- Standard verification: Included on every plan with no per-email fee, so the 40,000 standard checks don't change the monthly price.
- Deep verification: Pro includes 25,000 a month. If the company deep-verifies its 9,000 riskiest addresses, 16,000 remain for re-checks.
- Cost: $29 for one month, or $25 a month billed annually, which comes to $300 a year.
To compare with a credit-based tool, use this formula:
Cost = contacts × re-verifications per year × price per credit
Credit-based pricing matters most when you re-verify often. If the company re-verifies 40,000 contacts four times a year, the total is 40,000 × 4 = 160,000 credits, multiplied by the per-credit rate on the vendor's pricing page. Flat standard verification removes that multiplier for standard checks.
The trade-off runs the other way for small, one-off jobs. A team that verifies a few hundred addresses once a year may find a pay-as-you-go tool cheaper than any monthly plan.
Bottom line: Calculate with your own row count and re-verification frequency. Generic price comparisons mislead.
Which verifier fits your situation?
Choose by workflow, not by a universal ranking.
| Your situation | Lean toward | Why |
|---|---|---|
| You need your verifier to connect directly to your ESP or CRM | NeverBounce, if your platform has a documented connector | Avoids manual export and re-import |
| You verify in periodic batches and want predictable costs | Unlimited Verifier | Flat standard-verification allowance |
| You need to measure accuracy | Both | Disagreements between tools point to the risky addresses |
| You verify at signup | Either, via the email verification API and automation | Compare batch sizes and rate terms before committing; see real-time email validation |
| You want to inspect how checks work | Unlimited Verifier | Open-source engine on GitHub |
| You run email verification for ecommerce and SaaS with daily signups | Test both on your own traffic | Signup domain mix changes accuracy |
You can also reach a verification API key quickly if you're planning an API workflow. For a structured way to compare options, see our how to choose an email verifier guide.
Bottom line: The right verifier is the one whose results you can check against your own bounces, at a price you can predict.
What mistakes make accuracy results misleading?
- Trusting a single headline percentage as your bounce rate. It describes the vendor's test data, not your list.
- Testing only fresh signups. Recent addresses are the easiest to verify, so this flatters any tool.
- Counting catch-all as valid to make the numbers look better. Those addresses are where bounces cluster.
- Ignoring the unknown bucket. Unknowns are unverified. Treating them as valid inflates your apparent clean rate.
- Verifying once and sending months later. For planning, re-verify lists older than about 90 days before major sends, as part of your email list maintenance best practices. The 90-day window is our recommendation, not a published standard.
- Assuming verification proves consent. A valid address can still be unconsented. Both email verification compliance and hygiene and the FTC's CAN-SPAM guidance concern lawful sending, not just clean addresses.
- Losing free-plan results. Unlimited Verifier's Free plan keeps results for 24 hours, so download them the same day.
Bottom line: Most accuracy disputes come from testing the wrong sample or treating uncertain labels as certain.
How we compared (and limitations)
This article is based on public documentation: NeverBounce's website and published descriptions of its result labels, Unlimited Verifier's published plan facts, the SMTP standards in RFC 5321 and RFC 3463, and the sender guidance cited above. We have not run a controlled benchmark of NeverBounce, and we make no claim about its measured accuracy.
Vendor pricing, plan limits and feature lists change, so check current pages before you decide. The worked-example figures are hypothetical and exist to show the arithmetic. The 99.5% accuracy figure for Unlimited Verifier's deep verification is the company's own stated figure, not an independent benchmark. Mailbox provider behaviour changes over time, which can shift any verifier's results.
Bottom line: Use this article as a method for testing accuracy on your own list, not as a verdict on any vendor's headline claim.
Measure your false-valid rate in 4 steps
- Verify your full list and export the addresses labelled valid.
- Draw a random sample of 300 to 500 valid addresses, excluding catch-all ones.
- Send a normal campaign to the sample and record hard bounces after 48 hours.
- Calculate: false-valid rate = bounced sample addresses / sample size.
| Result | Action |
|---|---|
| Under 1% | Keep sending, re-check quarterly |
| 1% to 2% | Review catch-all and unknown segments |
| Over 2% | Tighten thresholds or switch verifier |
Frequently asked questions
Is NeverBounce accurate for invalid emails?
Yes, NeverBounce is most dependable when it flags addresses as invalid. Syntax errors, missing domains and rejected mailboxes give clear evidence, so invalid results are the labels to trust most. The costlier risk is a dead address marked valid, which is why you should measure the false-valid rate on your own list.
What is a false valid email result?
A false valid is an address the verifier labels deliverable that then bounces when you send to it. It hurts sender reputation because bounces feed into your ESP's bounce rate. Track it as valid-labelled addresses that bounce divided by valid-labelled addresses you mailed.
Does NeverBounce work on catch-all domains?
Catch-all domains accept mail for any address, so a probe cannot confirm a specific mailbox exists. NeverBounce's labels for these domains are less reliable, so treat catch-all results as risky rather than safe. Send to them with care and monitor their bounce rate separately.
What does unknown mean in NeverBounce?
Unknown means the verifier could not get a clear answer from the receiving server, often because it blocked or delayed the check. Unknown results carry real uncertainty. Treat them as risky, and avoid counting them as verified when you calculate deliverability.
How accurate is NeverBounce compared to other email verifiers?
Accuracy depends on your list's domain mix, age and engagement, so a single comparison rarely transfers. Run the same sample through two verifiers and compare their false-valid rates against actual bounces. That result is more useful than any vendor's headline figure.
What bounce rate should I aim for after verification?
A common planning target is keeping bounces on the valid segment under 1% and total bounces under 2%. These are practical guardrails rather than universal standards, so adjust them to your ESP's policies and your own sending history.
Should I remove catch-all and unknown addresses?
Not automatically. Removing all of them can cut reach significantly, but mailing them without caution can raise bounces. A middle path is to send to them in small batches, watch bounces closely, and suppress any that bounce or show no engagement.
How do I test NeverBounce accuracy myself?
Pick a random sample of a few hundred valid-labelled addresses, send a real campaign, and count hard bounces. Divide those bounces by the sample size to get your false-valid rate. Repeat with a fresh sample over time, since list quality and provider behaviour change.
Is NeverBounce's accuracy claim independently verified?
Not in this guide. NeverBounce publishes its accuracy claims on its website, but those are vendor figures based on its own test data. Check the current page for the method behind any percentage before relying on it.
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.