Article
ClearOut vs ZeroBounce: Which Email Verifier Fits Your List?
By Unlimited Verifier Team ·

Summary
ZeroBounce publicly documents spamtrap, abuse and do_not_mail statuses, making it the safer first look for cold outreach, while ClearOut's public material doesn't confirm its full status set. For warm lists, measure each tool's false-valid rate on your own 1,000-address sample and aim for 1% or lower.ZeroBounce and ClearOut both clean bulk lists by checking syntax, domains, mail servers and mailboxes, but ZeroBounce publicly documents spamtrap and abuse statuses that ClearOut's public material doesn't confirm, which makes it the safer first look for cold outreach. For warm lists, the deciding factor is different: measure each tool's false-valid rate on your own 1,000-address sample and aim for 1% or lower.
Quick answer
- ZeroBounce documents spamtrap, abuse and do_not_mail statuses, so it has the most published trap detail of the two. Cold senders should start there.
- ClearOut is positioned around bulk cleaning and API access. Confirm its full result set and spam-trap handling in writing before you buy.
- Vendor accuracy claims aren't comparable. Score each tool on your own data: hard bounces among Valid-labelled addresses ÷ all Valid-labelled addresses. Target 1% or lower.
- Model the 12-month cost, not one pass. A 40,000-row list at a hypothetical $8 per 1,000 costs $320 once and about $704 over a year with 10% monthly re-verification.
- Unlimited Verifier includes unlimited standard verification on every plan, with Pro at $29/month or $25/month billed annually. It doesn't advertise spam-trap statuses and has no native connectors, so cold senders should add a trap check.
What do ZeroBounce and ClearOut actually check?
Both tools run the same core pipeline: a syntax check, a domain and MX lookup, and an SMTP mailbox probe. The probe opens a conversation with the recipient's mail server and asks whether the mailbox exists, without delivering a message. RFC 5321 defines that conversation. The verifier's real work is interpreting the answer, and that's where the tools differ.
Some answers are unambiguous. Others aren't. A catch-all server accepts mail for any local part, so it never confirms a specific mailbox. Greylisting, rate limits and full mailboxes add more uncertainty. How a tool labels this middle ground determines what you can safely send.
- ZeroBounce documents statuses including valid, invalid, catch-all, unknown, spamtrap, abuse and do_not_mail. Its sub-statuses include disposable, role-based and toxic. The company also describes activity data and AI-based scoring as engagement signals.
- ClearOut publicly describes bulk list cleaning and API access. From public material, we couldn't confirm its full status set or whether it flags spam traps, so verify both directly.
- Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox, detects catch-all domains, flags disposable and role-based addresses, and sorts results into Valid, Risky and Invalid. It doesn't advertise spam-trap detection.
Why this matters: a hard bounce is a permanent failure. RFC 3463 defines enhanced status code 5.1.1 as a bad destination mailbox, and every one of those bounces counts against your sender reputation. Google's sender guidelines advise keeping spam rates below 0.10% and avoiding rates of 0.30% or higher. A list full of dead addresses or traps pushes you toward both problems.
Bottom line: Both tools answer "does this mailbox exist?", but they label the uncertain middle differently, and that label decides what you can send to safely.
Which is more accurate, ZeroBounce or ClearOut?
Neither accuracy headline can be compared directly, because each vendor tests on different data and defines "correct" differently. Some count a catch-all address as a success when it is labelled Risky. Others count an Unknown result as a miss. Those choices move the headline number without changing what reaches your inbox.
Unlimited Verifier states 99.5% accuracy for its deep verification. That is the company's own figure, not an independent benchmark.
The metric that predicts deliverability is the false-valid rate:
False-valid rate = hard bounces among Valid-labelled addresses ÷ total Valid-labelled addresses
We recommend a 1% acceptance bar. If your Valid bucket is 3% dead, your first sends will push bounces toward the 2% total-bounce ceiling that reviewers commonly watch, leaving little margin. The 2% and 1% figures are planning numbers we recommend, not thresholds published by any ESP.
Sample size matters. At 95% confidence, the margin of error on a proportion is about 1.96 × √(p(1−p)/n). For a 2% rate, a 200-address sample gives roughly ±1.9 percentage points. A 1,000-address sample narrows that to about ±0.9 points, which is enough to separate two tools one point apart.
Ground truth is imperfect. A past hard bounce is strong evidence that an address is invalid. A non-bounce doesn't prove validity, because a full mailbox or an accepting catch-all server can hide a dead address. Recent engagement is the best positive signal available.
Bottom line: Ignore vendor accuracy headlines, measure the false-valid rate on your own addresses, and aim for 1% or lower.
How do ZeroBounce, ClearOut and Unlimited Verifier compare side by side?
The table uses only what public documentation supports. Cells marked "confirm" are details we couldn't verify, so check them before you decide.
| Criterion | ZeroBounce | ClearOut | Unlimited Verifier |
|---|---|---|---|
| Result categories | Documented: valid, invalid, catch-all, unknown, spamtrap, abuse, do_not_mail | Confirm the full set | Valid, Risky, Invalid |
| Spam-trap and abuse flags | Documented as status values | Confirm | Not advertised; pair with a separate trap check |
| Disposable and role-based flags | Documented as sub-statuses | Confirm | Flagged in results |
| Catch-all detection | Documented as its own status | Confirm | Detected and flagged; confirm the bucket in your export |
| Engagement data | Activity data and AI scoring, per the company | Confirm | Not in the described feature set; segment with your own engagement data |
| Pricing | Confirm current bundles and per-check rates | Confirm current plans and per-check rates | Unlimited standard verification on all plans; Free $0; Pro $29/month or $25/month billed annually |
| File input and output | Confirm file limits | Confirm file limits | CSV or Excel up to 10MB, email column auto-detected; export CSV, Excel or JSON |
| API | Documented by the company | Confirm | Pro includes API access (100,000 emails/month); single checks and batches of up to 10,000 per request |
| Native ESP or CRM connectors | Check the company's current list | Check the company's current list | None; export, verify, re-import, or call the API |
| Result retention | Confirm | Confirm | Free: 24 hours. Pro: 30 days |
Where each one falls short for your use case:
- ZeroBounce's trap and abuse statuses matter most for cold outreach. On a warm newsletter list, those extra statuses change little about the send decision.
- ClearOut's open questions are the point to resolve. Ask for written documentation of its statuses and trap handling before you commit to a plan.
- Unlimited Verifier has no spam-trap statuses and no native connectors. Every refresh is an export, verify and re-import loop, unless you script the email verification API.
Bottom line: ZeroBounce has the most documented trap detail, ClearOut needs confirming on your side, and Unlimited Verifier suits predictable bulk CSV cleaning.
How should you handle catch-all and Risky addresses?
A catch-all domain accepts mail for any local part, so the server never confirms that a particular mailbox exists. A verifier can tell you the domain accepts mail, but not that your contact is a real person there. Measure your catch-all share instead of guessing it, because B2B lists often contain a meaningful portion.
Every send plan should follow three buckets:
- Valid: send now, starting with the most engaged contacts.
- Risky: hold back. This bucket typically covers catch-all, disposable, role-based and uncertain results.
- Invalid: remove and suppress permanently.
The tool's categories matter here. If a tool isolates traps and complainer-linked addresses, you can keep them out of cold sends without touching the Risky group. If a tool pools everything uncertain into one Unknown or Risky bucket, you have to decide what to do with a mixed group. Either approach can work, but only the first tells you why an address is risky.
For Unlimited Verifier, the catch-all email verification page explains how catch-all domains are handled. Route Risky results into a separate segment, and use email verification API and automation patterns if you need to route results on every signup or import.
Bottom line: Treat Risky as a hold segment, and choose the tool whose uncertain categories match the decisions you need to make.
What does each option cost per 1,000 emails over a year?
Cost per pass is simple arithmetic: list size ÷ 1,000 × price per 1,000 emails. The email verification pricing that matters is the total you pay across a year, because lists decay as people change jobs and mailboxes close.
12-month cost = first pass + (12 × monthly re-verified volume × price per email)
Vendor pricing changes often and is structured differently across credit bundles, subscriptions and check types. Use your own current quote in these formulas, and check each vendor's pricing page before you rely on any number. Before you compare, ask each vendor in writing whether any check type costs more per address, since deep, catch-all or trap checks may be priced differently.
If you're comparing budget options alongside these two, MillionVerifier vs NeverBounce shows how price and check depth trade off in that pairing.
Bottom line: Compare on a 12-month model with re-verification included, not on the price of a single pass.
How do you run your own ClearOut vs ZeroBounce test?
This framework takes about a day and produces a number you can defend. Use the same steps for any two tools.
- Build a stratified sample of 1,000 addresses from past sends. Include 400 that hard-bounced and 600 that delivered and showed recent opens. Exclude anything with no clear outcome, and keep the file so you can rerun it.
- Deduplicate and suppress known complainers. Keep a copy of your suppression data, because verification results don't carry over when you change platforms.
- Run both tools on the same day. Results can drift over time, so same-day runs keep the comparison fair.
- Map each vendor's statuses to Valid, Risky and Invalid in writing. Decide where catch-all, unknown, disposable and trap statuses land, and apply the same rule to both tools.
- Score two numbers. The false-valid rate (hard bounces among Valid-labelled addresses ÷ all Valid-labelled addresses) and the catch rate (known-bad addresses labelled Invalid or Risky ÷ all known-bad addresses).
- Compare cost on the 12-month formula from the previous section.
- Decide with a rule. Choose any tool whose false-valid rate is at or under 1%. If both pass, choose the one whose uncertain categories match your sending plan.
Worked example (hypothetical numbers): The sample holds 400 known-bad and 600 known-good addresses.
- Tool A labels 585 known-good addresses Valid and 20 known-bad addresses Valid. Its Valid bucket is 605, so its false-valid rate is 20 ÷ 605 = 3.3%. It labels 380 of the 400 known-bad addresses Invalid or Risky, a catch rate of 95%.
- Tool B labels 590 known-good addresses Valid and 5 known-bad addresses Valid. Its Valid bucket is 595, so its false-valid rate is 5 ÷ 595 = 0.8%. It catches 395 of 400, a catch rate of 98.8%.
Tool B clears the 1% bar and Tool A doesn't, even though Tool A's catch rate is respectable. The sample also shows why the false-valid rate matters more than the catch rate: Tool A's extra false Valids are what would bounce on your first send.
For a broader shortlist to test, see the best email verification tools roundup and our how to choose an email verifier checklist.
Bottom line: Score the false-valid rate on your own data, because it predicts what your first sends will do.
Where does Unlimited Verifier fit?
Unlimited Verifier suits teams that clean many lists quickly and need predictable costs. Unlimited standard verification is included on every plan, with no per-email fees. Pro adds unlimited lists of up to 25,000 emails each, 25,000 deep verifications a month, and API access at 100,000 emails a month. Ecommerce and SaaS teams that clean CSV exports on a schedule are the clearest fit, a use case covered in email verification for ecommerce and SaaS.
It is a weaker fit in two situations: when spam-trap detection drives the decision, or when you need native connectors to your ESP or CRM. For cold outreach, run a separate trap check alongside it.
You can test it at no cost first. The Free plan covers 25 lists a month of up to 150 emails each, plus 750 deep verifications a month. A 1,000-address bake-off sample splits into seven files of up to 150 rows each (1,000 ÷ 150 = 6.7, rounded up to 7), well within the 25-list monthly allowance. Two limits to plan around: Free results are kept for 24 hours, and the Free plan has no API access.
You can sign up for a free account, or try the free email checker on individual addresses.
Bottom line: Unlimited Verifier is the most predictable bulk option in this comparison, and it needs a trap check added for cold outreach.
How do you sort a list into Valid, Risky and Invalid?
- Export your contacts as a CSV from your ESP or CRM. Include the email column and any engagement fields, such as last open date, so you can segment later.
- Create an account. Start on the Free plan if you're testing, and begin with a 150-row file.
- Upload the file on the upload and verify a list page. Accepted formats are CSV or Excel up to 10MB, and the email column is detected automatically.
- Split large files to fit the per-list cap. On Pro, each list holds up to 25,000 emails. A 40,000-row export needs two files, such as 25,000 and 15,000.
- Run verification. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all domains are flagged, and disposable and role-based addresses are marked.
- Read the three buckets. Send Valid addresses now. Hold Risky addresses, which typically include flagged catch-all, disposable and role accounts such as info@. Confirm exactly where catch-all results land in your first export. Remove Invalid addresses.
- Export the results as CSV, Excel or JSON, and save the summary counts. They go straight into your records and into any compliance review.
- Re-import only Valid contacts as a new segment, and add Invalid addresses to your ESP's suppression list. The email verification compliance and hygiene guidance explains how to document this step.
Bottom line: Export, verify, send Valid, hold Risky, suppress Invalid, and keep the counts.
Worked example: cleaning a 40,000-row list over a year
Scenario: A SaaS company has a 40,000-row list and expects about 10% of it to decay each month, so 4,000 addresses need re-verifying monthly. The price for the per-credit vendor is hypothetical. The Unlimited Verifier figures are its published plan terms.
Path A: per-credit vendor at a hypothetical $8 per 1,000 emails
- First pass: 40,000 ÷ 1,000 × $8 = $320
- Monthly re-verification: 4,000 ÷ 1,000 × $8 = $32
- 12-month total: $320 + (12 × $32) = $704
Path B: Unlimited Verifier Pro
- Split the list into a 25,000-row file and a 15,000-row file, each under the per-list cap.
- Standard verification of all 40,000 addresses carries no per-email fee.
- Use the 25,000 monthly deep verifications on the riskiest 25,000 addresses, and run the remaining 15,000 with standard verification.
- Monthly re-verification of 4,000 addresses fits within the 25,000 deep quota.
- 12-month total: $29 × 12 = $348 on monthly billing, or $25 × 12 = $300 on annual billing.
Why Free doesn't work for this list: 40,000 ÷ 150 = 266.7, so the list needs 267 files. The Free plan allows 25 lists a month, or 3,750 emails. Free is for testing, not for a list this size.
Compare with care. Path A's price is hypothetical, so the result is only as good as the quote you get. Path B's deep allowance caps at 25,000 a month, so if your busiest month needs more deep checks than that, plan the schedule around it.
Bottom line: Model the full year rather than one pass, and check that your busiest month fits inside the deep-check allowance.
Which should you choose?
Let your sending model decide. Cold outreach points toward trap detection, and high-volume CSV cleaning points toward predictable pricing.
| Your situation | Start with | Why |
|---|---|---|
| Cold B2B outreach where spam traps are the top risk | ZeroBounce, validated through your bake-off | Documents spamtrap and abuse statuses; compare its false-valid rate on your data. See ZeroBounce vs MillionVerifier for cold email |
| Ecommerce or SaaS cleanup on a monthly schedule | Unlimited Verifier Pro | Unlimited standard checks, predictable pricing, CSV or Excel export. Add a trap check for cold sends |
| Validation inside a signup flow | Compare APIs; Unlimited Verifier Pro includes 100,000 API emails a month | Batches of up to 10,000 per request. See real-time email validation |
| Native connector to your ESP with no scripting | ZeroBounce or ClearOut, per their current connector lists | Unlimited Verifier has no native connectors, so expect a manual export-import loop |
| Testing before committing | Unlimited Verifier Free | 150-row files, 25 lists a month; export results within 24 hours |
If neither tool fits, best ZeroBounce alternatives and Bouncer vs ZeroBounce cover the closest options. Buyers who lean toward Kickbox should read top Kickbox alternatives before deciding.
Bottom line: Match the tool to the sending decision you make most often, and validate that choice with your own false-valid rate.
Common mistakes to avoid
- Choosing on headline accuracy. Different test sets make those numbers incomparable. Measure the false-valid rate on your own addresses.
- Testing on addresses with no known outcome. Without ground truth, you can't score anything. Build the sample from past hard bounces and recent engagement.
- Treating Risky as Valid to hit volume. Catch-all addresses can bounce, and sending to them early damages the reputation you're trying to repair.
- Ignoring the catch-all share in your cost model. If a large share of the list lands in Risky, your effective sendable list shrinks, and that changes your send calendar.
- Assuming trap detection exists. Check the status list for spamtrap and abuse values before you rely on them. A tool without those statuses isn't unsafe in every use, but it can't answer the trap question for you.
- Losing Free-plan results. They're kept for 24 hours, so export them immediately.
- Dropping suppression history during a migration. Export your bounce and complaint suppressions, and keep your own copy.
- Verifying once and stopping. Lists decay, so re-verify on a schedule. Email list maintenance best practices sets out a cadence you can follow.
Bottom line: Most bad outcomes come from scoring the wrong metric or skipping the re-verification cycle.
How we compared (and limitations)
This comparison is based on public documentation from each vendor, plus the public standards and guidance cited above. We have not run controlled tests against ZeroBounce or ClearOut, and we haven't confirmed ClearOut's current status set, spam-trap handling, connectors or pricing from public material. Vendor pricing and features change, so confirm them on each vendor's site before you buy.
Unlimited Verifier's figures come from its own published plan details. The 99.5% deep-verification accuracy is the company's stated figure, not an independent benchmark. The costs in the worked examples are hypothetical and exist to show the arithmetic. The 10% monthly decay rate is an assumption for the example, not a benchmark.
Sources also disagree on exact bounce and complaint cut-offs, and platforms set their own thresholds. We recommend a 2% total-bounce ceiling and a 1% false-valid acceptance bar as planning numbers, then measuring against your own results. For regulatory context, consult the FTC's CAN-SPAM compliance guide for US mail, the UK's Information Commissioner's Office if you email UK recipients, and M3AAWG for industry best practice on sender hygiene.
For the bigger picture, see our guide to email verifier alternatives.
12-month cost model
Hypothetical rate: $8 per 1,000 emails.
| Scenario | Rows | Cost |
|---|---|---|
| One-time clean | 40,000 | $320 |
| 12 months, 10% monthly re-verify | 40,000 + recurring | about $704 |
Steps:
- Price one full pass of your list.
- Multiply by expected re-verification volume per month.
- Multiply by 12 and add the one-time cost.
- Compare the annual total across vendors, not the first invoice.
Frequently asked questions
Is ZeroBounce more accurate than ClearOut?
Neither vendor's accuracy claim can be compared directly because each uses its own methodology. The fair test is to verify a 1,000-address sample from your own list with both tools and measure the share of Valid-labelled addresses that hard bounce. Aim for 1% or lower.
Does ClearOut detect spam traps?
From the public material reviewed, we could not confirm that ClearOut flags spam traps. Ask the vendor in writing which statuses it returns and how it handles trap addresses before buying, especially for cold outreach.
What is a false-valid rate?
A false-valid rate is the number of hard bounces among addresses a verifier labelled Valid, divided by all Valid-labelled addresses. It measures how often a tool's safe label turns out to be wrong, and it is the most useful accuracy metric for comparing verifiers.
What is a catch-all domain?
A catch-all domain is a mail server configured to accept mail for any local part, so a verifier cannot confirm whether a specific mailbox exists. Tools typically label these addresses as catch-all or risky rather than valid.
How much does email verification cost per 1,000 emails?
Pricing varies by plan, volume and re-verification frequency. Use a hypothetical rate to model cost: at $8 per 1,000, a 40,000-row list costs $320 once, and roughly $704 over a year with 10% monthly re-verification.
Does Unlimited Verifier detect spam traps?
Unlimited Verifier does not advertise spam-trap detection. Cold senders should run an additional trap check or use a tool that documents trap statuses, since verification alone does not guarantee trap-free output.
What hard bounce code means a mailbox does not exist?
RFC 3463 defines enhanced status code 5.1.1 as a bad destination mailbox. Hard bounces with this code count against sender reputation, so removing addresses that return it is essential.
How often should I re-verify an email list?
Re-verify when list data ages, typically before major campaigns and on a recurring schedule for active lists. Modelling monthly re-verification at 10% of the list shows how recurring costs can exceed the one-time cleaning cost.
What spam rate should bulk senders stay under?
Google's sender guidelines advise keeping spam rates below 0.10% and avoiding rates of 0.30% or higher. Dead addresses and spam traps push senders toward those thresholds, which is why verification matters.
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.