Article
MillionVerifier vs NeverBounce: Pricing, Catch-All and Accuracy Compared
By Unlimited Verifier Team ·

Summary
MillionVerifier and NeverBounce run largely the same core checks: syntax, domain/MX and mailbox. The real difference lies in cost per usable address, how catch-all and unknown results are handled, API limits and retention. Testing both tools on a sample of your own list with known outcomes is the most reliable way to choose.MillionVerifier and NeverBounce run largely the same core checks (syntax, domain/MX and mailbox) in bulk, so the real decision comes down to cost per usable address, catch-all policy and API fit at your volume.
The overlap is also why the choice is hard. Once two tools run the same checks, the differences show up in edge cases: pricing units, how catch-all and unknown results are handled, API limits, native integrations and how long results are kept. This guide shows you how to test MillionVerifier, NeverBounce and Unlimited Verifier on your own data and read the results, rather than deciding from a feature grid.
Quick answer
- The core checks overlap. Public documentation for all three describes syntax, domain/MX and mailbox checks. The differences are pricing units, catch-all policy, API limits, integrations and retention.
- Compare cost per usable address. Divide total spend by the Valid addresses returned. A lower per-check rate can still cost more.
- Measure false-valid rate on your own list. Test 1,000 addresses with known outcomes. We recommend a ceiling of 1% before you re-mail a list.
- Set your catch-all policy before you test. It often moves your bounce rate more than headline accuracy figures do.
- Unlimited Verifier Pro ($29/month, or $25/month billed annually) includes unlimited standard verification and lists of up to 25,000 emails each. It suits flat-rate, file-based cleaning, but test it against your alternatives.
What do MillionVerifier and NeverBounce have in common?
Both take a list, check each address and return a status for every row. The mailbox check works by opening an SMTP conversation with the recipient's mail server and asking whether it would accept mail for that address. The protocol is defined in RFC 5321.
The server's reply is a signal, not a guarantee. Some domains accept every address (catch-all). Some block or rate-limit probes. Some return temporary responses that clear up later. That is why most bulk verifiers include an "uncertain" category.
The reply codes are worth understanding. RFC 3463 defines enhanced status codes. A 5.1.1 means the destination mailbox is bad, a permanent failure. A 4.x.x code is a temporary failure, and many unknown results come from these. When you judge a verifier, ask how it handles temporary responses, because that decides how many addresses land in the uncertain bucket.
Bottom line: The checks overlap, so the decision turns on how each tool handles uncertainty.
How do the three tools compare side by side?
| Factor | MillionVerifier | NeverBounce | Unlimited Verifier |
|---|---|---|---|
| File upload | Bulk list upload (confirm current file limits) | Bulk list upload (confirm current file limits) | CSV or Excel up to 10MB; email column detected automatically |
| Result categories | Publicly described as valid, invalid, catch-all, disposable and unknown (labels differ) | Publicly described as valid, invalid, catch-all, disposable and unknown (labels differ) | Valid, Risky or Invalid; catch-all domains detected; disposable and role-based addresses flagged |
| Pricing model | Credit-based (confirm current rates) | Credit-based plans (confirm current rates) | Free ($0) or Pro ($29/month, or $25/month billed annually); standard verification unlimited on every plan |
| Limits | Confirm on vendor site | Confirm on vendor site | Free: 25 lists a month of up to 150 emails each. Pro: unlimited lists of up to 25,000 emails each, plus 25,000 deep verifications a month |
| API | Available (confirm limits) | Available (confirm limits) | Pro only: 100,000 emails a month; single checks and bulk batches of up to 10,000 per request |
| Native integrations | Confirm on vendor site | Publishes a list of native integrations | None; export CSV, verify, re-import, or call the API |
| Result retention | Confirm on vendor site | Confirm on vendor site | Free: 24 hours. Pro: 30 days |
| Notable detail | Confirm on vendor site | Owned by ZoomInfo | Publishes its verification engine as open source on GitHub |
Where a cell says "confirm", we could not verify that detail from public documentation, so we left it out rather than guess.
Bottom line: Use the table to shortlist, then decide on the rows that match your workflow: pricing unit, catch-all handling, API limits, integrations and retention.
How do you compare pricing fairly?
Compare cost per usable address: total spend divided by the number of Valid addresses returned. A headline rate tells you what you pay per check, not what you keep. How email verification pricing is structured determines how that number moves.
Confirm four things with each vendor before comparing:
- What is billed. Some tools charge for every address submitted, others only for definitive results.
- Whether uncertain results use credits. If catch-all and unknown addresses are billed, a catch-all-heavy list costs more per usable address.
- Whether credits expire. Expiry changes the real cost of a one-off clean.
- Where volume tiers start. Per-address rates often fall at larger bundles, so price at your volume.
The arithmetic below uses placeholder rates for two hypothetical vendors. These are not quotes from any vendor.
- Vendor A: $4.00 per 1,000 checks. 60,000 addresses return 50,000 Valid.
- Spend: 60,000 ÷ 1,000 × $4.00 = $240
- Cost per 1,000 Valid: $240 ÷ 50 = $4.80
- Vendor B: $3.00 per 1,000 checks. 60,000 addresses return 46,000 Valid, because more land in catch-all or unknown.
- Spend: 60,000 ÷ 1,000 × $3.00 = $180
- Cost per 1,000 Valid: $180 ÷ 46 = $3.91
Vendor B wins here. The lesson is that the usable count decides, not the rate. If Vendor B returned only 37,000 Valid, its cost would be $180 ÷ 37 = $4.86 per 1,000 Valid, and Vendor A would be cheaper.
A flat subscription has no per-address rate, so divide the monthly fee by Valid addresses. The 38,000-contact example later in this guide does this for Unlimited Verifier Pro.
Bottom line: Divide spend by Valid addresses returned. That figure is what you are buying.
How should you handle catch-all and unknown results?
Set this policy before you test, because the catch-all share of your list decides how far two tools diverge. A catch-all domain accepts mail for any address, so a "yes" from its server does not confirm a mailbox. An unknown result means the server gave no clear answer, often because of timeouts, greylisting or probe blocking. Neither is safe to treat as Valid, and neither is necessarily dead.
| Result | What it usually means | Recommended action |
|---|---|---|
| Valid | Mailbox accepted the check | Send, starting with the most engaged contacts |
| Invalid | Mailbox rejected | Suppress permanently |
| Catch-all | Domain accepts every address | Hold back; send only to contacts with recent engagement, in small tests |
| Disposable | Throwaway address service | Suppress for B2B; set a deliberate policy for consumer lists |
| Role-based (such as info@) | Shared inbox, often not read by one named person | Hold back from personalised campaigns |
| Unknown | No clear answer from the server | Re-verify later; don't mail until it resolves |
Unlimited Verifier detects catch-all domains and flags disposable and role-based addresses, and its results come back as Valid, Risky or Invalid. Check how your export categorises each flag before you build send lists. The catch-all email verification page explains how these domains are handled.
The practical distinction is engagement. A catch-all address that opened or clicked in the last 90 days has earned a careful test send. One with no engagement has not, whatever the verifier's label says.
Bottom line: Decide the catch-all policy first. The verifier's label only tells you which list an address belongs to.
Which tool is more accurate for your list?
Vendor accuracy figures are hard to compare because each vendor usually measures against its own data. Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark. We know of no public, like-for-like benchmark covering all three tools on the same list, so measure your own.
Track two error types:
False valid: the verifier says Valid, but the address bounced. This raises your bounce rate and is the dangerous error.
False invalid: the verifier says Invalid, but the address was delivered and engaged. This costs reach, not deliverability.
False-valid rate = bounced addresses marked Valid ÷ all bounced addresses
False-invalid rate = delivered addresses marked Invalid ÷ all delivered addresses
Here is a hypothetical sample of 1,000 addresses (500 bounced, 500 delivered):
- Vendor X: 30 of 500 bounced marked Valid, a 6.0% false-valid rate. 15 of 500 delivered marked Invalid, a 3.0% false-invalid rate.
- Vendor Y: 4 of 500 bounced marked Valid, a 0.8% false-valid rate. 35 of 500 delivered marked Invalid, a 7.0% false-invalid rate.
Vendor Y protects your bounce rate. Vendor X keeps more reachable contacts. Before re-mailing a list after a bounce problem, rule out any tool with a false-valid rate above 1%. That rules out Vendor X.
Two sample-design rules matter. Only hard bounces coded 5.1.1 count as known-invalid. A soft bounce, such as a full mailbox, is not proof the address is dead. And score catch-all domains separately, because a delivered message on a catch-all domain does not prove the mailbox exists.
Bottom line: Measure your own false-valid rate. Vendor figures are no substitute for it.
Which API and integration model fits your stack?
Choose the workflow that matches how your data moves:
- Scheduled list cleans. Export a CSV, upload it, export results and re-import. This works with any tool that offers bulk upload and suits monthly or quarterly hygiene.
- Signup validation. Each address is checked as it enters. This needs an API with a response fast enough for a form. The real-time email validation guide covers the design choices.
- Automated pipelines. Your scripts call the email verification API and automation on each import or on a schedule. The email verification API page explains how keys work.
Native integrations matter if your team doesn't write code. NeverBounce publishes a list of native integrations, so check that your ESP or CRM is on it. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so its workflow is export, verify, re-import, or API calls from your own scripts. Confirm MillionVerifier's integrations on its site.
On Unlimited Verifier's API, the Free plan has no API access. Pro includes 100,000 API emails a month, with single-email checks and bulk batches of up to 10,000 per request. A 25,000-row list therefore needs three requests (10,000 + 10,000 + 5,000). Batch sizes and monthly quotas often differ from file limits, so check each vendor's documentation.
Bottom line: Without developers, integrations decide. With developers, API quota and batch size decide.
How do you run a bake-off in one afternoon?
This test takes about an afternoon and uses your own delivery data as ground truth. You can sign up for a free account and run the same steps with any other vendor.
- Build a labelled sample. Export 500 addresses with hard bounces coded
5.1.1from your ESP's bounce log. Export 500 addresses that were delivered and opened in the last 90 days. Leave out soft bounces. - Strip the file to two columns. Keep email and outcome (bounced or delivered). The test doesn't need anything else, so don't upload other personal data.
- Plan the upload size. On Free, each list holds up to 150 emails, so 1,000 addresses need 7 lists (1,000 ÷ 150 = 6.67, rounded up). Free allows 25 lists a month, so the test fits. Pro takes the full sample as one list.
- Upload and verify. Use Upload and verify a list. The email column is detected automatically.
- Export the same day. Free results are kept for 24 hours and Pro results for 30 days. Export as CSV, Excel or JSON.
- Repeat with the second vendor using the identical 1,000 addresses.
- Join results to outcomes. Match on email in a spreadsheet, then count false valids and false invalids using the formulas above.
- Investigate disagreements. Use the Free email checker on individual addresses where the tools disagree.
- Record cost per usable address for each vendor: total spend ÷ Valid addresses.
- Rerun one batch on another day. Unknown results can change between runs. If they do, you learn how stable each tool is.
Bottom line: A 1,000-address test with known outcomes tells you more than any comparison table, including this one.
Which one should you choose?
There is no universal winner. The right tool is the one with the lowest false-valid rate and cost per usable address on your data, and it has to fit your workflow.
| Your situation | What to prioritise | Where to start |
|---|---|---|
| Developers building signup checks | API quota, batch size, response time | Unlimited Verifier Pro's API (100,000 emails a month, batches up to 10,000); compare the others' API limits |
| No developers; checks inside your ESP or CRM | Native integrations | NeverBounce publishes integrations, so confirm yours is listed. Unlimited Verifier requires CSV export and re-import |
| One-off clean of files up to 25,000 rows each | Cost per usable address | Unlimited Verifier Pro for one month at $29, against credit quotes from the others |
| Small lists and testing | Plan limits | Free plan: 25 lists a month of up to 150 emails each, no API |
| Monthly re-verification | Whether re-checks cost extra | Unlimited standard verification has no per-email fee on any plan |
| B2B lists with many catch-all domains | False-valid rate on a sample with catch-all scored separately | Bake-off with catch-all kept separate |
Cold email senders should read ZeroBounce vs MillionVerifier for cold email before deciding. If your shortlist is wider, these head-to-heads help:
- Best ZeroBounce alternatives
- Bouncer vs ZeroBounce and Clearout vs ZeroBounce
- Top Kickbox alternatives
- EmailListVerify alternatives and competitors
For the wider market, see the best email verification tools roundup and how to choose an email verifier.
Bottom line: Let your bake-off result and your workflow decide, not the feature grid.
What would this look like for a 38,000-contact database?
This is a hypothetical SaaS company with 38,000 contacts: 29,000 from product signups and 9,000 from a trade-show import. It needs to clean the whole database before a new campaign. Work like this is common in email verification for ecommerce and saas programmes.
Step 1: Check whether Free fits. 38,000 ÷ 150 = 253.3, so 254 lists. Free allows 25 lists a month, which caps the month at 3,750 emails. Free can't do this list.
Step 2: Split the file for Pro. 25,000 + 13,000 = 38,000. Each list is within the 25,000-email cap, and standard verification is unlimited.
Step 3: Spend the deep-verification allowance. Pro includes 25,000 deep verifications a month. Put the 9,000 imported leads through deep verification, which leaves 16,000 for re-checks.
Step 4: Or use the API. 38,000 ÷ 10,000 = 3.8, so 4 requests (10,000 + 10,000 + 10,000 + 8,000). That is well within Pro's 100,000 monthly API emails.
Step 5: Read the hypothetical outcome.
- Valid: 30,020 (79.0%)
- Risky: 4,940 (13.0%)
- Invalid: 3,040 (8.0%)
The three segments add up to 38,000.
Step 6: Cost it. $29 for the month. $29 ÷ 30.02 (thousands of Valid) = $0.97 per 1,000 Valid addresses. That excludes staff time, and the per-address cost falls as volume rises within Pro's per-list cap.
Step 7: Plan the re-entry. Send first to Valid contacts who engaged in the last 30 days, then the 90-day group, then the rest. Hold Risky addresses back. Suppress Invalid ones. A 13% Risky share is large, so decide how you'll re-check those before you send.
For ongoing hygiene after the clean, see email list maintenance best practices.
Bottom line: A flat fee looks cheap per usable address only if the false-valid rate holds up on your list. Measure that first.
What should you check on data retention and compliance?
Retention and data use belong in the comparison. Ask each vendor these questions before you upload live contacts:
- How long are files and results kept? Unlimited Verifier keeps results for 24 hours on Free and 30 days on Pro.
- Is uploaded data used for anything besides returning results? Get the answer in writing.
- Will the vendor sign a data processing agreement? Under GDPR Article 28, a processor handling personal data on your behalf needs a written agreement. Ask for one if you hold EU or UK contacts.
Verification is not consent. A valid mailbox is not an opted-in contact. The FTC's CAN-SPAM compliance guide sets the baseline for commercial email in the US, and email verification compliance and hygiene covers the wider practice. If you're weighing a specific vendor's reputation, read Is MillionVerifier legit? before uploading.
Deliverability sets a separate limit. Google's sender guidelines ask bulk senders to keep user-reported spam below 0.10% and to avoid reaching 0.30%. Yahoo's sender requirements use 0.3% as their threshold. Sources differ on the exact line, so we recommend one number: keep complaints below 0.10%. A verifier that lets bad addresses through pushes you toward those limits.
Bottom line: Get retention and data-use terms in writing before you upload a live contact list.
What mistakes do teams make when comparing email verifiers?
- Mixing temporary and permanent bounces in the sample. A soft bounce from a full mailbox is not proof the address is invalid, and it skews the false-valid measurement.
- Counting catch-all deliveries as proof. A delivered message on a catch-all domain confirms the server accepted mail, not that the mailbox exists.
- Running the test once. Unknown results can change between runs, so rerun a batch on another day.
- Comparing flat plans with credit plans on headline rate. Divide spend by Valid addresses for both.
- Letting Free-plan results expire. Free results are kept for 24 hours, so export the same day.
- Assuming native integrations exist. Unlimited Verifier has none, so check that any tool you consider supports your stack.
- Uploading more personal data than the test needs. Reduce the file to email and outcome.
- Treating a verified address as a consented one. Verification does not replace opt-in.
Bottom line: Most bad comparisons fail on the denominator (usable addresses) or the sample (no known outcomes).
How we compared (and limitations)
This article is based on public documentation: each vendor's published descriptions, RFC 5321 and RFC 3463 for SMTP behaviour, and Google's and Yahoo's sender requirements. We have not run controlled tests against MillionVerifier or NeverBounce, and we have not verified their current prices, API limits, file limits, integration lists or retention terms. Check each vendor's current site before you decide.
Unlimited Verifier details come from the company's published plan facts. The 99.5% deep-verification accuracy figure is the company's own claim. The 1,000-address bake-off, the Vendor A and B rates and the 38,000-contact example use hypothetical numbers to show the arithmetic. They are not measured results.
For a broader view, start with the email verifier alternatives pillar. If Emailable is also on your list, its review covers pricing separately.
Cost per usable address
- Note total spend for the test run.
- Count addresses returned as Valid.
- Divide spend by Valid count.
| Tool | Spend | Valid returned | Cost per usable address |
|---|---|---|---|
| Tool A (illustrative) | $100 | 8,000 | $0.0125 |
| Tool B (illustrative) | $80 | 6,000 | $0.0133 |
In this illustrative case, Tool A is cheaper per usable address despite a higher total spend.
Frequently asked questions
Is MillionVerifier more accurate than NeverBounce?
Neither tool is consistently more accurate across every list. Accuracy depends on your domain mix, catch-all share and how temporary responses are handled. Run both on 1,000 addresses with known outcomes and compare false-valid rates on your own data.
Which is cheaper, MillionVerifier or NeverBounce?
The cheaper option depends on credit pricing, volume and how many addresses come back valid. Divide total spend by valid addresses returned to get cost per usable address, since a lower per-check rate can still cost more overall. Confirm current rates on each vendor's pricing page.
What is a catch-all domain in email verification?
A catch-all domain accepts mail for any address at that domain, so the server reply does not prove a specific mailbox exists. Verifiers usually label these separately, and your policy for them strongly affects bounce rates.
Should I remove catch-all addresses from my list?
Not automatically. Removing them lowers bounce risk but may discard real customers. Many senders mail catch-all addresses cautiously, with engagement tracking, while removing addresses that show invalid or hard-bounce results.
What does an unknown result mean in email verification?
Unknown usually means the receiving server gave a temporary or inconclusive response, blocked the probe or rate-limited the check. It is not proof the address is bad or good, so you should decide in advance how to handle this bucket.
Does MillionVerifier or NeverBounce have an API?
Both offer APIs for real-time or programmatic verification, as described on their public documentation. Compare rate limits, concurrency, response formats and integration options against your sending stack before committing.
How often should I verify my email list?
Verify before large sends, after importing new sources and periodically for older lists, since addresses decay over time. The right cadence depends on how quickly your list changes and how often you mail it.
Is Unlimited Verifier a good alternative to MillionVerifier and NeverBounce?
Unlimited Verifier offers flat-rate pricing with unlimited standard verification on its plans, which suits file-based cleaning at high volume. It should be tested against the others on your own data, because flat pricing is only cheaper if its accuracy and limits fit your list.
How do I test email verifiers fairly?
Build a sample of about 1,000 addresses with known outcomes, run each tool on the same file, and compare valid, invalid and uncertain results against your ground truth. Track cost per usable address and false-valid rate, not just headline accuracy claims.
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.