Article
ZeroBounce vs MillionVerifier for Cold Email: Accuracy and Cost Compared
By Unlimited Verifier Team ·

Summary
For cold email, ZeroBounce suits teams that need named spam-trap and abuse statuses and will pay more for that depth. MillionVerifier is the lower-cost choice for teams that can triage uncertain results themselves, and a labelled bake-off on about 1,000 addresses is the fairest way to decide.For cold email, ZeroBounce is the stronger pick if you need named spam-trap and abuse statuses, while MillionVerifier is the lower-cost option for teams willing to judge uncertain results themselves. Neither tool can guarantee a clean send, so the real test is how each one labels your own list. This comparison sits within our wider guide to email verifier alternatives.
Cold lists are where the differences show. A newsletter built from opt-ins decays slowly. A scraped or purchased prospect list carries far more risk per row, and that is the lens for everything below.
Quick answer
- Choose ZeroBounce if you want explicit spam-trap and abuse categories and will pay more per check for that depth, as its public documentation describes.
- Choose MillionVerifier if cost per check dominates and someone on your team will triage the uncertain results.
- Run a bake-off on about 1,000 addresses with known outcomes before committing. Error rates on a labelled seed set tell you more than how often two tools agree.
- Target under 2% bounces on every send, and under 0.1% spam complaints.
- Unlimited Verifier is a third option if you want a simple Valid / Risky / Invalid split, unlimited standard verification and an API. It does not list spam-trap detection among its checks, so keep your own trap hygiene in place.
Why is cold email harder to verify than newsletter lists?
Cold lists fail verification more often because the people on them never asked to hear from you. That creates three problems.
First, scraped, enriched or purchased lists have no engagement history, so the verifier's answer is often the only evidence you have. Second, B2B prospect lists lean heavily on company domains, and many of those run catch-all servers that accept mail for any local part. A verifier can confirm the domain takes mail but cannot confirm that the individual mailbox exists. Third, data that is months old contains people who have changed jobs, and their old addresses may now be dead or reassigned.
Spam traps add a different risk. These are addresses operated to catch senders who mail without permission or keep dead contacts. No verifier can promise to flag every trap, so treat trap detection as risk reduction, not a guarantee.
For outbound teams, the uncertain bucket usually decides how much work you do, more than the obvious invalids do. Cold programmes often sit inside wider email verification for ecommerce and SaaS workflows, where B2B addresses churn quickly.
Bottom line: Cold lists are riskier per row, so the uncertain results (catch-all, unknown, trap-like) matter more than the obvious invalids.
What should a cold-email verifier actually catch?
A cold-email verifier should catch five things, and each one maps to a different decision.
- Syntax and domain errors, such as
gmial.com. A domain with no MX record cannot receive mail, so a send to it is a near-certain bounce. - Mailbox existence, checked over SMTP. Receiving servers reply with enhanced status codes.
5.1.1means a bad destination mailbox, as defined in RFC 3463. Some servers won't confirm individual mailboxes, which is why catch-all results exist. - Catch-all detection, which separates addresses you can prove from ones you cannot.
- Disposable and role-based addresses, such as
info@orsales@. Role accounts are shared by several people, so they rarely suit a personal cold sequence. - Trap and abuse signals. These are useful but not universal, so check whether a tool reports them at all.
The practical test is whether the output tells you what to do with each row. If two categories trigger the same action, the extra granularity is wasted money.
Bottom line: Prioritise tools whose categories map directly to a send decision, with catch-all and role addresses clearly separated.
How do ZeroBounce and MillionVerifier compare side by side?
Both tools cover the core checks. They differ in which risk signals they name and how they price. The table reflects each vendor's public documentation at the time of writing. Category names and plans change, so confirm them on the vendor's site before you buy.
| Dimension | ZeroBounce | MillionVerifier |
|---|---|---|
| Core checks (syntax, MX, SMTP mailbox) | Covered in its public documentation | Covered in its public documentation |
| Catch-all handling | Dedicated catch-all status | Dedicated catch-all result |
| Spam-trap and abuse signals | Named statuses in its documentation | Not a headline category in its public documentation |
| Engagement or scoring signals | Describes AI scoring and activity data | Not a headline feature in its public documentation |
| Pricing model | Credit-based | Credit-based, positioned as low-cost at volume |
| Best fit | Teams that want risk signals before launch | Teams optimising cost per check |
ZeroBounce: where it earns its price
- Named trap and abuse statuses. According to its documentation, these give you an exclusion reason beyond "invalid", which helps when you later need to explain why a row was removed.
- Scoring and activity data. ZeroBounce states that it offers AI-based scoring and activity signals to help rank contacts. For a list with no engagement history, that extra signal is the main thing it adds.
- Drawback: You pay for those deeper signals on every check, even if your policy only acts on Valid and Invalid. A team with a three-way policy may never use part of what it pays for.
MillionVerifier: where it earns its keep
- Low, pay-as-you-go credit pricing. It is generally positioned as a budget option for large one-off cleans, which suits a list you clean once and rarely touch again.
- Simple result labels. Its API documentation centres on results such as ok, invalid, catch-all, unknown and disposable. These map straight onto send and suppress decisions. Confirm the current labels, because they can change.
- Drawback: With fewer trap and abuse categories in its public documentation, more of the risk judgment falls on you. The unknown bucket also needs a written policy, or it quietly becomes part of your send list.
Bottom line: ZeroBounce gives you more risk labels to act on. MillionVerifier gives you a cheaper, simpler sort that puts more of the judgment on your team.
How do the result categories change your send plan?
Each category should trigger one action. This mapping works for most cold programmes:
- Valid: send, in ramped batches.
- Invalid: suppress permanently.
- Catch-all or unknown: hold back, and test in small batches only.
- Disposable or role-based: exclude from personal cold sequences.
- Trap or abuse flags, where your tool reports them: exclude and record the reason.
The size of the uncertain bucket determines your real cost. If a tool returns 15% of a 40,000-row list as unknown, that is 6,000 addresses you cannot send to with confidence. You then have to pay to re-check them, accept the risk, or discard them. A verifier that labels fewer addresses as uncertain is not automatically more accurate. It may simply be making bolder calls, and your bake-off should measure exactly that.
Bottom line: Judge a verifier by how much of your list it leaves uncertain, not only by how much it marks invalid.
What does a verified address really cost?
Price per 1,000 checks is the wrong metric for cold email. Use cost per 1,000 sendable addresses instead:
Cost per 1,000 sendable = price per 1,000 checked ÷ share classified Valid
These prices and shares are hypothetical, chosen to show the method rather than any vendor's rates:
- Tool A: $8 per 1,000 checked, 70% Valid → $8 ÷ 0.70 = $11.43 per 1,000 sendable
- Tool B: $5 per 1,000 checked, 60% Valid → $5 ÷ 0.60 = $8.33 per 1,000 sendable
Tool B is cheaper here. Drop its Valid share to 45% and it becomes $5 ÷ 0.45 = $11.11, which costs more than Tool A. Re-checks of uncertain addresses add to the total, so compare the full cost of a clean list rather than a single pass. Check current email verification pricing on each vendor's site before running the sum.
Bottom line: The cheapest check is not the cheapest clean address. Divide the price by the share you can actually send to.
Which verifier fits your cold-email scenario?
Choose by scenario rather than by a general ranking. If you are still mapping the market, best email verification tools gives the wider field, and our how to choose an email verifier checklist covers the selection criteria.
| Scenario | Lean toward | Why |
|---|---|---|
| One-off clean of a large scraped list, budget first | MillionVerifier | Low cost per check, and your team owns the triage |
| Agency launching cold campaigns that need trap and abuse reasons | ZeroBounce | Named statuses give you an exclusion reason for each row |
| Small team with 5,000–25,000 prospects and a simple three-way policy | Unlimited Verifier, or either tool after a bake-off | Valid / Risky / Invalid maps onto three actions |
| Product team validating sign-up addresses at the point of entry | An API-first workflow | Checks run as people sign up, as described in real-time email validation |
Bottom line: Match the tool to your volume, your need for trap signals, and whether anyone on your team will work the uncertain bucket.
Where does Unlimited Verifier fit?
Unlimited Verifier is a bulk verifier that checks syntax, domain and MX records, and the SMTP mailbox. It detects catch-all domains, flags disposable and role-based addresses, and sorts every address into Valid, Risky or Invalid. For cold email, three things stand out:
- Unlimited standard verification on every plan, including Free, with no per-email fees. Re-checks after a cleanup or a bake-off add no per-address cost. You can test on the free tier after you create a free account.
- Catch-all detection, which covers the segment cold lists generate most. Its catch-all email verification page explains how those results are handled.
- An API for single-address checks and bulk batches of up to 10,000 emails per request. API access is included on Pro, which covers 100,000 API emails a month. Use the email verification API when verification has to run inside your own scripts. For workflow patterns, see email verification API and automation.
The company states 99.5% accuracy for deep verification. That is Unlimited Verifier's own figure, not an independent benchmark, so check it against your seed set.
The honest limitations are:
- No spam-trap detection among its listed checks, so keep trap hygiene in your process.
- No native ESP, CRM or Zapier integrations. You export a CSV, verify it and re-import it, or call the API.
- Results expire. They are kept for 24 hours on Free and 30 days on Pro, so export before the window closes.
- Bucket placement needs checking. Catch-all, disposable and role-based addresses are detected, but review a sample of your export to see how they land on your list before you write send rules around them.
Bottom line: Unlimited Verifier suits a three-way sort with unlimited standard checks. Pair it with your own trap controls and a manual import step.
How do you run a bake-off on your own list?
A bake-off tells you more than any comparison article, including this one. Its job is to measure false negatives, which are the errors that hurt you most.
- Build a seed set of 200 labelled addresses. Use 100 known-good addresses, such as prospects who replied to recent outreach or your own test inboxes. Add 100 known-bad addresses, such as past hard bounces and deliberate misspellings of real domains like
name@gmial.com. - Add 800 unlabelled addresses from your real cold list, for 1,000 in total.
- Run all 1,000 through each tool. On Unlimited Verifier's Free plan, 1,000 addresses fit into seven lists of up to 150 emails (six full lists and one of 100), within the 25-lists-a-month allowance.
- Score the seed set. Count false negatives, meaning known-bad addresses marked Valid. These are the dangerous errors, so the target is zero. Count false positives, meaning known-good addresses marked Invalid. These cost you good prospects.
- Measure the uncertain share of the 800 real addresses, meaning catch-all, unknown and risky results. A tool that leaves 30% uncertain hands you extra work.
- Compute cost per 1,000 sendable with the formula above.
- Confirm with a small live send. Send 200 addresses that both tools marked Valid and measure the bounce rate. Stay under 2%. A live send is the most direct evidence mailbox providers will ever give you about your list.
If Bouncer is also on your shortlist, our Bouncer vs ZeroBounce comparison covers that pairing.
Bottom line: Score on false negatives first, then on uncertain share and cost per sendable address, and confirm with a live send.
How do you verify a cold list with Unlimited Verifier?
- Export your prospects as a CSV from your prospecting or enrichment tool. Make sure the email address sits in its own column.
- Clean the email column. Remove stray spaces, blank rows and exact duplicates. Hidden characters can make a deliverable address fail parsing, which produces a false Invalid.
- Create an account. Start on the free plan to test, or go straight to Pro if the list is large.
- Split the file to fit your plan. On Free, each list holds up to 150 emails, and you get 25 lists a month. On Pro, each list holds up to 25,000 emails.
- Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically.
- Triage the three buckets. Send Valid addresses in ramped batches, suppress Invalid addresses, and hold Risky addresses back for testing.
- Export the results as CSV, Excel or JSON. Download them before the retention window closes: 24 hours on Free, 30 days on Pro.
- Re-import only Valid contacts into your sending tool as a new segment. Add Invalid addresses to its suppression list so they are never mailed.
To spot-check a single address before it enters a sequence, use the free email checker.
Bottom line: Clean the column, split to your plan's cap, verify, triage, export before results expire, and re-import only the Valid addresses.
What does a cleaning run look like on the Pro plan?
This example uses hypothetical results. The plan limits are real.
Starting point: 40,000 unique scraped prospects, with no previous sends to this list.
Split: Two files, 25,000 and 15,000 rows, both within the Pro per-list cap.
Cost: Standard verification of all 40,000 is included, with no per-email fees. Pro is $29 a month, or $25 a month billed annually. If this list is the only job that month, $29 ÷ 31,000 Valid addresses works out to about $0.94 per 1,000 sendable ($25 billed annually gives about $0.81). Other work in the same month lowers that figure.
Deep verifications: Pro includes 25,000 a month. Use 6,000 on the Risky segment and keep the remaining 19,000 for later checks.
Hypothetical results:
- Valid: 31,000 (77.5%)
- Risky: 6,000 (15.0%)
- Invalid: 3,000 (7.5%)
Check: 31,000 + 6,000 + 3,000 = 40,000.
Why cleaning matters: Sending all 40,000 would put 3,000 invalid addresses into the send. That alone is a 7.5% bounce rate (3,000 ÷ 40,000), well above the 2% ceiling.
Re-entry plan:
- Send 1: 31,000 Valid addresses. At a 1% bounce rate, that is 310 bounces (310 ÷ 31,000 = 1%), under the 2% ceiling. Ramp across several batches rather than sending all at once.
- Send 2: 300 Risky addresses as a test. At a 2% ceiling, the limit is 6 bounces (300 × 2% = 6). If you stay within it, release the next batch. If not, stop and reassess the segment.
Bottom line: Cleaning moves the expected bounce rate from 7.5% to a level you can hold under 2%, for less than one Pro month.
What bounce and complaint numbers should you target?
Sources differ on exact thresholds, so here is what each says and what to aim for.
- Bounces: Amazon SES's documentation describes a 5% bounce rate as a review point and 10% as a level at which sending may be paused. Other platforms act earlier, sometimes on a single campaign. Recommended target: under 2% total bounces, and under 1% for your first sends.
- Spam complaints: Google's sender guidelines ask bulk senders to keep spam rates below 0.10% in Postmaster Tools and never let them reach 0.30%. Recommended target: under 0.1%, which leaves you headroom before the 0.30% line.
Where sources differ, use the stricter number as your operating target. Cold email generates more bounces and complaints per send than opt-in mail, so you need the headroom.
Bottom line: Target under 2% bounces and under 0.1% complaints. Those numbers keep a cold programme alive.
What are the common mistakes?
- Choosing on price per check alone. Compare cost per 1,000 sendable addresses instead.
- Sending to catch-all or unknown addresses first. They belong at the end of your ramp, in small test batches.
- Losing results to the retention window. Free results expire after 24 hours, so export the same day.
- Skipping the seed set. Without known-good and known-bad addresses, you measure agreement between tools, not error rates.
- Treating "Valid" as permission. A deliverable address is not a permitted one. Under the US FTC's CAN-SPAM compliance guide, commercial email needs an working opt-out, accurate headers and a valid postal address. In the UK, the ICO enforces PECR, which generally requires consent before marketing to individual subscribers, while corporate subscribers follow a lighter regime. Verification cannot supply your legal basis. Get advice for your specific situation.
- Re-verifying endlessly. Once a list is clean, a small live send tells you more than another pass of checks.
- Ignoring repeated 5.1.1 bounces. They point to a sourcing problem, not a tool problem. Fix where the addresses come from, and see email list maintenance best practices for ongoing hygiene.
- Comparing tools on public features alone. Two tools with similar feature lists can label the same list very differently. Run the bake-off. If you are weighing a second pairing, ZeroBounce alternatives and MillionVerifier vs NeverBounce show how other tools compare on the same criteria.
Bottom line: The expensive mistakes rarely sit in the tool. They sit in how you score it, what you send first, and whether you have a lawful basis to send at all.
How we compared (and limitations)
This comparison is based on public documentation from ZeroBounce and MillionVerifier, Amazon SES's published thresholds, Google's sender guidelines, RFC 3463 for SMTP status codes, and M3AAWG best-practice guidance. We have not benchmarked either tool's accuracy or run controlled tests against either service. Feature lists, category names and prices change, so check each vendor's current site before deciding.
The 99.5% accuracy figure is Unlimited Verifier's own stated figure for deep verification, not an independent test. Every price, share and bounce percentage in the worked examples is hypothetical and exists to show the arithmetic.
Bottom line: Use the framework and the bake-off to decide. Published features cannot tell you which tool is more accurate on your list.
Bake-off steps for choosing a verifier
- Build a seed set of about 1,000 addresses with known outcomes (confirmed delivered, confirmed bounced, known catch-all).
- Run the same seed through ZeroBounce and MillionVerifier.
- Compare each tool's labels against the known outcomes and count false valids and false invalids separately.
- Weigh error rates against cost per check at your expected volume.
- Pilot the winner on one small cold batch and track bounce rate and complaints before scaling.
Frequently asked questions
Is ZeroBounce better than MillionVerifier for cold email?
Neither tool is better in every case. ZeroBounce is the stronger choice if you need named spam-trap and abuse statuses, while MillionVerifier costs less per check. Run a bake-off on about 1,000 addresses with known outcomes to see which labels your list more accurately.
How much does ZeroBounce cost per check?
Pricing changes over time and depends on plan and volume, so check the current pricing page on the ZeroBounce website before budgeting. Compare the effective cost per verified address at your expected volume, not just the headline rate.
How much does MillionVerifier cost per check?
MillionVerifier sells credit-based plans that lower the per-check cost at higher volumes. Confirm current rates on its official pricing page, since they change. Factor in the time your team spends reviewing uncertain results.
Can an email verifier guarantee no bounces?
No. Verifiers estimate deliverability and cannot confirm every mailbox, especially on catch-all domains. Aim to keep bounces under 2% on every send and treat verification as risk reduction.
What is a catch-all email address?
A catch-all address belongs to a domain whose server accepts mail for any local part, so the server reports every mailbox as valid. Verifiers can confirm the domain accepts mail but usually cannot confirm the individual person exists.
What is a spam trap?
A spam trap is an address operated to catch senders who mail without permission or keep dead contacts. Some traps are recycled old addresses. No verifier can promise to flag every trap, so keep list hygiene strong.
Should I remove catch-all addresses from a cold list?
Not automatically. Catch-all addresses are uncertain rather than invalid. Many teams send to them cautiously in small batches and monitor bounces and complaints before scaling.
Does Unlimited Verifier detect spam traps?
Based on its public documentation, Unlimited Verifier offers a Valid, Risky or Invalid split and does not list spam-trap detection among its checks. Keep your own trap hygiene in place if you use it for cold outreach.
What bounce rate is safe for cold email?
Many senders aim to keep bounces under 2% and spam complaints under 0.1% per send. Treat these as working targets to monitor, not official thresholds from any provider.
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.