Article
Bouncer vs ZeroBounce: Statuses, Spam Traps and Cost Compared
By Unlimited Verifier Team ·

Summary
Bouncer and ZeroBounce both check whether an email address can receive mail, but ZeroBounce's documented API returns seven primary statuses, including spamtrap and abuse, while Bouncer uses four results: deliverable, risky, undeliverable and unknown. Choose ZeroBounce for granular trap and abuse labels, and Bouncer for faster three-way triage, then confirm the choice with a test on your own bounce history.Bouncer and ZeroBounce both check whether an address can receive mail, but ZeroBounce's documented API returns seven primary statuses, including spamtrap and abuse, while Bouncer uses a leaner set of deliverable, risky, undeliverable and unknown. For most bulk cleans, the choice is between granular trap-and-abuse labels and faster three-way triage, and a test on your own bounce history will settle it faster than any spec sheet. Our email verifier alternatives guide covers the wider market. This page narrows the decision to these two tools and to Unlimited Verifier, which we publish, so read our product claims with that in mind.
Quick answer
- Choose ZeroBounce when a list's origin is uncertain or purchased, because its documented statuses include spamtrap and abuse as separate categories.
- Choose Bouncer when triage speed matters more than label depth and you want fewer statuses to map.
- Score both on your own bounce history. Vendor accuracy figures come from vendor test data. With 1,000 addresses per class, a two-point gap is usually not statistically conclusive.
- Compare cost per clean, not price per 1,000. Cost = list size × passes per year × price per credit.
- Unlimited Verifier offers unlimited standard verification on every plan, including Free, so repeat passes add no per-email fee. Deep verification is quota-based: 750 a month on Free and 25,000 on Pro.
What do Bouncer and ZeroBounce actually return?
Both return a status for each address, and that status decides what you can safely mail. ZeroBounce's API documentation lists seven primary statuses (valid, invalid, catch-all, unknown, spamtrap, abuse and do_not_mail), each with sub-status codes. Bouncer's public documentation, as we read it, uses four results: deliverable, risky, undeliverable and unknown. Labels change, so confirm them on each vendor's site before you build rules around them.
| Criterion | ZeroBounce | Bouncer | Unlimited Verifier |
|---|---|---|---|
| Primary result statuses | Seven, including spamtrap, abuse, do_not_mail | Four: deliverable, risky, undeliverable, unknown | Three: Valid, Risky, Invalid |
| Spam-trap handling | Dedicated spamtrap status | No dedicated trap category in the docs we read | No spam-trap category in its verified feature set |
| Disposable and role flags | Sub-status codes | Reported within results | Flagged on every address |
| Catch-all domains | Catch-all status | Risky-type result | Detected and sorted into Risky |
| Pricing model | Credits, per public pricing | Credits, per public pricing | Unlimited standard on all plans; deep verifications quota-based |
| API | Yes | Yes | Pro plan, 100,000 emails a month; bulk requests up to 10,000 emails |
| Native ESP/CRM integrations | Check current list | Check current list | None; export, verify and re-import, or call the API |
The strengths and weak spots are specific to each tool:
- ZeroBounce. Its finer labels let you route traps and abuse hits separately. The cost is complexity: seven statuses mean more mapping work, and the extra detail helps only if your suppression rules use it.
- Bouncer. Fewer labels make triage quick. The trade-off is that one risky bucket hides why an address is risky, so an engaged contact on a catch-all domain sits next to a genuinely dangerous one.
- Unlimited Verifier. Standard checks are unlimited on every plan, and its verification engine is open source on GitHub, so you can inspect the logic. Its limits are real: no native integrations, no documented spam-trap category, and results kept only 24 hours on Free (30 days on Pro).
Bottom line: ZeroBounce offers the finer labels on paper, and Bouncer's leaner set is quicker to act on, as long as its risky bucket is reliable for your list.
How do you map each tool's labels to Valid, Risky and Invalid?
Mapping is where bounces leak through. Most teams skip it and treat any "not invalid" result as safe. The table below shows our suggested mapping for a three-bucket workflow.
| Bucket | ZeroBounce statuses | Bouncer results |
|---|---|---|
| Valid (mail now) | valid | deliverable |
| Risky (hold, review) | catch-all, unknown, do_not_mail | risky, unknown |
| Invalid (suppress) | invalid, spamtrap, abuse | undeliverable |
Two rules matter most. Treat spamtrap and abuse as suppress-permanently, never as "risky for later". Treat do_not_mail as a review item, because its meaning depends on the reason code your policy requires.
Bottom line: A mapping error that sends a trap address into your Valid bucket is the most expensive mistake in this comparison, so write the mapping down before the first upload.
Why do catch-alls, traps and role addresses decide the result?
Each category breaks a different assumption that verifiers rely on. Understanding why helps you judge any tool's output.
Catch-all domains. These mail servers accept any address during the SMTP check, so a "yes" tells you nothing about a specific mailbox. Treat catch-all results as Risky. Our catch-all email verification page explains how Unlimited Verifier handles them.
Spam traps. Traps are addresses run to catch senders who mail stale or purchased lists. A trap accepts the message, so an SMTP probe cannot reveal it. Detection relies on reputation and network data, which makes a "not a trap" label a probability, not a guarantee. A hard bounce carries an enhanced status such as 5.1.1 for a nonexistent mailbox, as defined in RFC 3463. Traps are the category that a bounce code alone cannot catch.
Disposable and role addresses. Throwaway domains and mailboxes such as info@ are real, but they rarely belong to a person who opted in. Put them in Risky for review, not in your first send.
Bottom line: Ask each vendor exactly how it handles catch-alls, traps and role addresses. Their answers matter more than an accuracy headline.
Which one is more accurate for your list?
Vendor accuracy numbers are measured on the vendor's own test data, and your list's age, source and geography will change the result. Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark, and the same caution applies to any competitor's number.
Measure two rates instead:
- False-valid rate: the share of addresses a tool labels Valid that actually bounce. This is the dangerous error, because it causes the bounce spike you are trying to avoid.
- False-invalid rate: the share of engaged addresses labelled Invalid. This costs you reach.
Sample size limits what you can conclude. At a true 7% false-valid rate, 1,000 addresses give a 95% margin of about ±1.6 points. Two tools that differ by two points on 1,000 addresses each are borderline, not proven. Repeat the test or enlarge the sample before you decide.
Bottom line: Judge verifiers on the false-valid rate measured against your own bounce history, and check that the gap is larger than the sampling noise.
How do you run a fair Bouncer vs ZeroBounce test?
A valid head-to-head needs about 2,000 addresses and a few hours. The key is using your own history as ground truth.
- Build a labelled sample. Take 1,000 addresses that hard-bounced in the last 12 months (expected: not deliverable) and 1,000 that opened or clicked in the last 90 days (expected: deliverable).
- Deduplicate and shuffle. Store the labels in a separate file that you never upload.
- Upload identical files to each tool. The same CSV means neither tool gets an easier input.
- Export results. Record the Valid, Risky and Invalid counts, plus any sub-statuses.
- Score against your labels. Count past bounces labelled Valid (false-valid) and engaged addresses labelled Invalid (false-invalid).
- Choose by false-valid first, then false-invalid, then cost.
Here is what scoring looks like with hypothetical numbers:
| Result on your sample | Tool A | Tool B |
|---|---|---|
| Past bounces labelled Valid (false-valid) | 70 of 1,000 = 7.0% | 95 of 1,000 = 9.5% |
| Engaged addresses labelled Invalid (false-invalid) | 40 of 1,000 = 4.0% | 25 of 1,000 = 2.5% |
In this illustration, Tool A protects your sender reputation better, and Tool B loses fewer real contacts. The 2.5-point false-valid gap only just clears the sampling noise, so repeat the test before acting on it.
Bottom line: A one-afternoon bake-off on your own bounce log tells you more than any published accuracy claim.
Hands-on: how do you test Unlimited Verifier on your sample?
- Export the sample as a CSV with only an email column. Keep the ground-truth labels in a separate file.
- Create a free account. Free covers 25 lists a month of up to 150 emails each. Your 2,000 addresses need 14 lists (2,000 ÷ 150 = 13.3, rounded up), well inside that cap. Free has no API access, so use the web upload for the test.
- Upload each file. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. Check that the detected column is your email field before you run.
- Let the checks run. Each address gets syntax, domain, MX and SMTP mailbox checks, plus catch-all, disposable and role flags.
- Read the three buckets for each list and record the Valid, Risky and Invalid counts.
- Export immediately as CSV, Excel or JSON. Free keeps results for 24 hours, so archive the file the same day.
- Score the results. Count only Valid results toward false-valid. For a quick spot-check of one address, use the free email checker.
Bottom line: Export and archive results the same day, because the retention window is short on Free and your archive is your only audit trail.
How much does each tool cost per clean?
The sticker price per 1,000 misleads because cost depends on how often you clean. The email verification pricing that matters is the annual cost of your passes:
Annual cost = list size × passes per year × price per credit
Consider a hypothetical rate of $3 per 1,000 credits. This is not either vendor's actual price:
40,000 contacts × 3 passes a year = 120,000 checks 120,000 ÷ 1,000 × $3 = $360 a year
Unlimited Verifier's Pro plan costs $29 a month, or $25 a month billed annually, which is $348 or $300 a year. Standard verification is unlimited, so extra passes add no per-email cost. At the hypothetical $3 rate, $300 buys 100,000 checks, or 2.5 passes of 40,000 contacts. Above that volume, the flat plan costs less per standard check. Deep verifications are a separate monthly quota, so compare standard checks like for like.
Bottom line: Model the passes you will actually run, because a flat plan with unlimited standard checks changes the math for repeat cleans.
Worked example: cleaning a 40,000-contact list
For an email verification for ecommerce and SaaS team, consider a B2B company with 40,000 contacts, 12,000 of them from a 2022 trade-show import. The team wants deep checks on the riskiest records and a fast pass on the rest.
Step 1: Respect the per-list cap. Pro allows lists of up to 25,000 emails each, so split the file:
List A: 25,000 (all 12,000 imported contacts plus the 13,000 oldest records) List B: 15,000 (recently engaged contacts)
Step 2: Allocate the deep quota. Pro includes 25,000 deep verifications a month. Running List A in deep mode uses that entire quota, so you have no headroom this month. Run List B with standard checks, which are unlimited. Schedule any deep re-run after the monthly reset.
Step 3: Read the results (hypothetical):
Valid: 31,200 (78%) Risky: 5,600 (14%) Invalid: 3,200 (8%) Total: 31,200 + 5,600 + 3,200 = 40,000
Step 4: Act on each bucket. Suppress the 3,200 Invalid addresses permanently. Re-import the 31,200 Valid addresses as a new segment. Hold the 5,600 Risky addresses, including catch-alls and role accounts, until the Valid send shows stable bounces.
Step 5: Archive and repeat. Pro keeps results for 30 days, so export the files the same day. Next quarter, the standard pass costs nothing extra per address, and the deep quota resets monthly. For ongoing hygiene, the email list maintenance best practices guide covers cadence.
Bottom line: Splitting to the per-list cap and spending the deep quota on the riskiest segment gives the most protection from one month's allowance.
Which tool should you choose? A decision framework
Answer these five questions. Your answers should decide the tool.
- Is the list purchased, scraped or of unknown origin? If so, ZeroBounce's documented spamtrap and abuse statuses give you labelled categories to act on. Unlimited Verifier does not document a spam-trap category, so treat its clean results as weaker evidence for these lists. Whichever verifier you use, the safer course is not to mail purchased or scraped lists at all.
- Will you clean repeatedly? If you run quarterly or monthly passes, unlimited standard checks on every plan reduce the cost of each pass. Credit-based pricing grows with every pass.
- Do you need checks at signup? Both competitors offer APIs. Unlimited Verifier's email verification API and automation is on Pro, with 100,000 emails a month and bulk requests of up to 10,000 emails. You can get an API key and see real-time email validation for form placement.
- Do you need native integrations? Unlimited Verifier has none. Its workflow is export, verify and re-import, or calling the API from your own scripts. Check competitors' current integration lists before deciding.
- Are you comparing a broader shortlist? See best ZeroBounce alternatives, Clearout vs ZeroBounce and Emailable vs ZeroBounce. For cold outreach, see ZeroBounce vs MillionVerifier for cold email. If Debounce is also in play, see Debounce alternatives. For a wider field, see how to choose an email verifier.
If you run two tools, send only the disagreements to manual review. That costs far less than a second full pass.
Bottom line: Choose ZeroBounce for trap-heavy or unknown-origin lists, Bouncer if triage speed matters most, and Unlimited Verifier when repeat passes and unlimited standard checks are the priority.
What are the common mistakes when comparing these tools?
- Comparing price per 1,000 instead of cost per clean. Ignoring the number of passes misstates the real cost.
- Testing with 200 addresses. At a 7% rate, that sample carries a margin of about ±3.5 points, too wide to separate two tools.
- Treating Risky as Valid, or discarding it without review. The first inflates bounces. The second throws away engaged contacts on catch-all domains.
- Mapping spamtrap or abuse to Risky. These must be suppressed permanently.
- Using a vendor's accuracy figure as the decision. Measure against your own bounce history.
- Ignoring result retention. Free keeps results for 24 hours and Pro for 30 days. Without an export, you have no audit trail.
- Ignoring plan limits. On Pro, lists cap at 25,000 emails each and deep verifications at 25,000 a month. Plan splits and quotas before you start.
- Verifying once. Lists decay as people change jobs and mailboxes close.
- Treating verification as consent. A valid address is not an opted-in address. The FTC's CAN-SPAM compliance guide still requires a working opt-out and accurate sender information. Verification supports email verification compliance and hygiene, but it does not replace consent.
Bottom line: Most bad comparisons measure the wrong thing: a sticker price, a tiny sample, or a vendor's own accuracy figure.
How we compared (and limitations)
This article is based on public documentation: each vendor's published API and pricing material, Unlimited Verifier's published plan facts, and the standards that define SMTP status codes. Relevant references include RFC 3463 for enhanced status codes, Google's bulk sender guidelines, and M3AAWG for messaging-hygiene practice. Vendor sites are ZeroBounce and Bouncer.
We have not run paid accounts, independent benchmarks or controlled tests against either competitor. Label sets, prices and integrations change, so verify them on each vendor's current site before you buy. All worked-example rates and results are hypothetical. The 99.5% accuracy figure is Unlimited Verifier's own claim, and the Unlimited Verifier plan details come from its published facts.
Bottom line: Decide on your own ground-truth data, and let the scoring, not the marketing, pick the winner.
Worked cost-per-clean example (illustrative)
Assume a 50,000-address list, cleaned 4 times a year, at an illustrative price of 0.005 per credit.
| Step | Calculation | Result |
|---|---|---|
| Credits per pass | 50,000 x 1 | 50,000 |
| Credits per year | 50,000 x 4 | 200,000 |
| Annual cost | 200,000 x 0.005 | 1,000 |
| Cost per clean | 1,000 / 4 | 250 |
Replace the illustrative price with each vendor's current per-credit rate and compare the cost per clean.
Frequently asked questions
Is Bouncer more accurate than ZeroBounce?
Neither vendor's accuracy figures settle this on their own. Published accuracy numbers come from vendor test data, and a gap of about two points is usually not statistically conclusive with around 1,000 addresses per class. Run both tools on a sample of your own list with known outcomes and compare the results.
Does ZeroBounce have a spam trap status?
Yes. ZeroBounce's documented API includes a dedicated spamtrap status, along with abuse and do_not_mail, among its seven primary statuses. This lets you suppress trap hits separately from ordinary invalid addresses. Confirm current status names on ZeroBounce's API documentation before building suppression rules.
Does Bouncer detect spam traps?
Based on the public documentation reviewed for this comparison, Bouncer does not list a dedicated spam-trap category. Its four results are deliverable, risky, undeliverable and unknown. Addresses that are risky for trap-like reasons would fall into the risky bucket, so check Bouncer's current documentation before relying on it for trap removal.
Which is cheaper, Bouncer or ZeroBounce?
Compare cost per clean rather than price per 1,000 addresses. Cost equals list size multiplied by passes per year multiplied by price per credit. Pricing changes often, so take each vendor's current credit prices from its public pricing page and run the formula for your real list size and re-verification frequency.
How do I choose between a three-way and seven-status verifier?
Choose a seven-status verifier such as ZeroBounce when list origin is uncertain or purchased, because separate trap and abuse labels let you act on them directly. Choose a simpler result set when your suppression rules only need to send, review or remove. More statuses only help if your rules actually use them.
What is a catch-all domain and how do these tools handle it?
A catch-all domain accepts mail for any address at that domain, so a server response alone cannot confirm a specific mailbox exists. ZeroBounce reports a catch-all status. Bouncer typically places such addresses in a risky-type result. Treat catch-all results as uncertain and decide whether to mail them based on engagement history.
Can I use Bouncer or ZeroBounce with my email platform directly?
Both offer APIs, so you can call them from custom scripts or integrations. Whether either has a native connector for your ESP or CRM changes over time, so check each vendor's current integrations list. If none exists, you can export a list, verify it, and re-import the cleaned results.
How often should I re-verify an email list?
Re-verify before each major campaign and whenever a list has aged, been imported from an outside source, or shows rising bounces. Many teams schedule a recurring pass rather than verifying once. The right frequency depends on how quickly your addresses decay, so use your own bounce data to set the interval.
Should I use one tool or run both?
Most teams use one verifier as the primary filter and keep the second for spot checks or disputed addresses. Running both on every address doubles cost without a clear gain unless your bounce history shows one tool misclassifying a specific segment. Test on a sample first, then decide whether a second opinion is worth paying for.
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.