Article

Can an Email Verifier Guarantee Zero Bounces? No, and Here's Why

By Unlimited Verifier Team ·

Flow diagram showing how an email verifier filters a list before sending, illustrating why verification cannot guarantee zero bounces.

Summary

No, an email verifier cannot guarantee zero bounces, because it checks an address at a single moment while bounces depend on the mailbox, the receiving server and your sender reputation at send time. The practical goal is a low, measured bounce rate on the addresses you actually send to, with under 1% as a sensible target.

No, an email verifier cannot guarantee zero bounces, even one that states 99.5% accuracy, because it checks an address at a single moment, while a bounce depends on the mailbox, the receiving server and your sender reputation at send time.

Unlimited Verifier states 99.5% accuracy for its deep verification, a figure the company publishes itself. If that rate applied to every address on a 100,000-row list, about 500 addresses would be misclassified. The realistic goal is a low, measured residual bounce rate on the addresses you actually send to. For the wider picture, read our pillar on email verifier accuracy.

Quick answer

Can an email verifier guarantee zero bounces?

No. A verifier removes most addresses that would bounce, but a bounce happens inside the receiving server at send time, and the verifier only sees that server's answer at an earlier point. Three gaps make zero impossible to promise:

Think of verification as a risk filter that improves your odds. The better question is: "What is my measured bounce rate on the addresses I send to, and is it under my ceiling?"

Bottom line: Verification lowers bounces predictably, but it cannot close the time, scope and policy gaps that exist at send time.

What does an email verifier actually check?

A verifier runs progressively deeper checks, and each layer rules out a different failure. Most tools run them in roughly this order.

Layer What it tests What it cannot tell you
Syntax Address format, such as a missing @ or illegal characters Whether the mailbox exists
Domain and MX Whether the domain has mail servers that can receive mail Whether the person still has a mailbox there
SMTP mailbox check Whether the receiving server accepts the recipient at the RCPT TO step Whether the mailbox fills, closes or starts rejecting mail later
Catch-all detection Whether the domain accepts any local part Which individual mailbox actually exists
Disposable and role flags Throwaway providers and shared inboxes such as info@ Whether the person wants your mail
Engagement recency (your own data, not a verifier check) Opens, clicks, purchases or signups Whether the address is deliverable today

The SMTP mailbox check is the strongest signal a verifier has, and the most misunderstood. The verifier opens a conversation with the domain's mail server, names the recipient and stops before any message body is sent. The server accepts or rejects the recipient under the rules in RFC 5321. Three limitations follow. Some servers accept every recipient. Some defer probes with temporary 4xx responses. And VRFY, the command designed to confirm a user directly, is frequently disabled.

A Valid result is therefore one accepted conversation, not a delivery guarantee. Does a valid result mean the email will be delivered? goes further into that gap.

Bottom line: The mailbox check is the best evidence a verifier has, but it is one conversation with a server, not a guarantee about a person.

Why do bounces still happen after verification?

Bounces survive verification for five main reasons. Each has a different cause and a different fix.

Catch-all domains hide the answer

A catch-all domain accepts mail for any address, real or invented, so an "accepted" response proves nothing about one mailbox. Unlimited Verifier flags catch-all domains so you can hold them back from your first sends. The catch-all email verification page explains how these results are handled.

Many B2B lists carry a higher share of catch-all domains than consumer lists, so a list that looks clean overall can hide most of its residual risk in that segment. Business domains on Microsoft 365 are one case where results are harder to read; how accurate verifiers are on Microsoft 365 addresses covers it. If many results come back uncertain, why so many unknowns? explains the usual causes.

Some receiving systems accept a message during the SMTP dialogue and only generate a bounce afterwards. A verifier reading "accepted" counts that address as Valid, and the bounce arrives later.

Mailboxes change between check and send

People leave companies, accounts get deleted and mailboxes get shut off. The longer the gap between check and send, the larger the residual risk. As a working rule, verify days before a send, not months before it.

Temporary failures look like success or nothing

A full mailbox returns the enhanced code 5.2.2, and an overloaded server returns a 4.x.x code meaning "try again later." RFC 3463 defines these enhanced status codes. A 4.x.x result is transient. A check may read as Risky or Unknown, or pass, and the state can change within hours.

Policy rejections depend on your reputation

Receiving providers can refuse mail with 5.7.x codes, such as 5.7.1 (delivery not authorized), based on sender authentication and reputation. A valid address will still bounce if your domain or IP reputation is poor, and no address-level check can see that.

Verifiers err in both directions

A false positive marks a bad address as Valid, and it bounces. A false negative marks a good address as Invalid, and you lose a real contact. Neither shows up until you compare results with actual sends. What a false positive looks like walks through spotting them. If two tools disagree on the same file, why different verifiers give different results explains the usual reasons.

Bottom line: Each residual bounce traces to one of these causes, and only some of them can be reduced by verifying harder.

Can a verifier catch spam traps?

Generally not reliably. A spam trap is an address run to catch senders who mail stale or unconsented lists, and it looks like a working mailbox to an SMTP check. The checks Unlimited Verifier describes (syntax, domain and MX, SMTP mailbox, catch-all detection, and disposable or role flags) do not include spam-trap detection.

That is why verification needs two companions. The first is removing contacts who have not engaged for a long time; email list maintenance best practices covers how to set that policy. The second is watching complaints. Google's sender guidelines treat spam-report rate as a separate measure from bounces, so track both.

Bottom line: Verification cannot reliably see spam traps. Sunsetting dormant contacts and monitoring complaints are the controls for that risk.

What do bounce codes tell you about a failure?

Log the SMTP code, not just the count. The code decides whether you suppress an address, retry it or fix your reputation. Receivers don't use codes consistently, so treat this table as a starting map.

Code Meaning (per RFC 3463) Could a pre-send check catch it? Action
5.1.1 Bad destination mailbox Usually yes Suppress permanently
5.1.2 Bad destination system (host or domain) Usually yes Suppress permanently
5.2.2 Mailbox full Sometimes; the state changes Retry later; suppress only if it repeats
4.x.x Temporary failure Rarely; it is a snapshot Retry, then suppress if it persists
5.7.1 Delivery not authorized or refused by policy No; it depends on your reputation Fix authentication and reputation; keep the address

Bottom line: Suppressing a 5.7.1 address because it bounced punishes the wrong party, and keeping a 5.1.1 address wastes sends.

Is 99.5% accuracy the same as zero bounces?

No, and the gap is instructive. Accuracy is measured on a labelled test set. Your bounce rate is measured on your list, with its own mix of domains and ages. Two points matter:

Unlimited Verifier states 99.5% accuracy for deep verification. Treat that as the company's own figure, not an independent benchmark. For how these numbers are generated and compared, see how accurate email verification really is and do email verifiers really have 99% accuracy?. For independent testing, see our independent accuracy benchmark.

Some vendors market "zero bounce" outcomes or bounce guarantees. Treat those as marketing, because no verifier controls the mailboxes it checks. If a vendor offers credits for bounces, read the terms to see exactly what counts. Are vendor accuracy claims trustworthy? shows how to read these claims.

Bottom line: A high accuracy figure describes the test. Your bounce rate describes your list, and only the second one matters for deliverability.

What bounce rate should you aim for?

Most providers don't publish thresholds, so there is no single industry number. The clearest public reference is Amazon SES's documentation, which describes a 5% bounce rate as the level that triggers account review and 10% as the level at which sending can be paused. Google's sender guidelines set expectations for spam complaints, which is a different measure, so keep the two apart.

Our recommendation:

Bottom line: Plan to stay under 1%, and treat 2% as the line you never cross.

How do you build a bounce budget?

A bounce budget turns "zero" into a number you can plan around:

Expected bounces = Σ (segment size × assumed residual bounce rate), and bounce rate = expected bounces ÷ total sends.

Start with assumed rates, then replace them with measurements from your first wave of sends. The rates in the worked example below are illustrative, not measured results.

Bottom line: A budget gives you a forecast you can check against reality, which makes a bounce spike easy to spot.

How do you verify a list and measure your residual bounce rate?

  1. Export your contacts from your ESP or CRM as a CSV, including the email column and fields such as last open, last click or purchase date. Export your suppression and bounce history separately and keep a copy, because verification tools don't carry your ESP's suppression list with them.
  2. Sign up and compare email verification pricing before choosing a plan. The Free plan allows 25 lists a month of up to 150 emails each, with 750 deep verifications and no API access. Pro is $29 a month, or $25 a month billed annually, with lists of up to 25,000 emails, 25,000 deep verifications a month and API access for 100,000 emails a month.
  3. Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. If your file exceeds the per-list cap for your plan, split it first.
  4. Run standard verification. It is unlimited on every plan, including Free, with no per-email fee. Spend your deep verification allowance on the segments where you most need certainty.
  5. Read the three buckets. Valid addresses are candidates for sending. Invalid addresses should be removed and suppressed. Risky addresses include catch-all, disposable and role-based results, and they should be held back.
  6. Export results immediately. Free-plan results are kept for 24 hours and Pro results for 30 days. Export as CSV, Excel or JSON, and save the summary counts.
  7. Re-import only Valid contacts into your ESP as a new segment, and add the Invalid addresses to your suppression list. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so this is a manual re-import, or you can call the API from your own scripts.
  8. Send a first wave to your most engaged Valid contacts. Log every bounce with its SMTP code and recipient domain, then compare the actual rate to your budget.
  9. Automate new data. Use the free email checker to spot-check a key account. For in-flow checks, the email verification API handles single-email checks and bulk batches of up to 10,000 emails per request. For patterns on wiring this into your systems, see email verification API and automation.

Bottom line: Verify, keep Valid, suppress Invalid, hold Risky, and measure the first wave before you scale.

What does a 100,000-contact list look like after verification?

Setup: A 100,000-contact list returns this illustrative result: 84,000 Valid, 9,000 Risky (7,500 catch-all and 1,500 disposable or role-based) and 7,000 Invalid.

Upload arithmetic

Cost arithmetic: One Pro month at $29 covers the run. $29 ÷ 100 = $0.29 per 1,000 emails if the whole list is verified in one month. Standard verification is unlimited, so re-running after cleaning adds no per-email charge.

Deep verification: Spend the 25,000 monthly allowance on the 9,000 Risky addresses and the 7,000 highest-value Valid addresses. That uses 16,000 and leaves 9,000 for spot-checks.

Bounce budget

Segment Contacts Assumed residual bounce rate Expected bounces
Valid (first wave) 84,000 0.30% 252
Catch-all Risky (small test after Valid) 7,500 5.0% 375
Disposable and role-based 1,500 Held back, not sent 0
Invalid 7,000 Removed 0
Total sent 91,500 627

Bounce rate: 627 ÷ 91,500 = 0.69%, under the 1% target and the 2% ceiling.

What "zero" would require: zero residual bounces from 84,000 Valid addresses. The 0.30% assumption expects 252, which is why the budget has a line for them.

Decision rule: If the measured Valid rate after the first wave reaches 1% or higher, stop the ramp, check your source data and investigate by code before sending more.

Bottom line: The budget converts "zero" into a planned 0.69% with a documented method, so you can defend the number when a reviewer asks.

Which approach gets closest to zero bounces?

No single step is enough. The approaches below work together, and each covers a gap the others leave open.

Approach What it reduces Limitation Best use
Verify before a send Invalid and unknown-mailbox bounces A snapshot that decays over time Baseline cleaning before a campaign
Verify at signup Typos and fake signups entering the list Can't stop a real address that closes later Forms and checkouts, via real-time email validation
Engagement segmentation Wasted sends to dormant contacts and exposure to residual risk Engagement data can be stale or missing First sends after cleaning
Double opt-in Mistyped and fake addresses; consent evidence Adds friction; some people never confirm Lists where consent proof matters
Scheduled re-verification Decay from closed mailboxes and job changes Needs a repeating process and an owner Active senders, monthly or quarterly

Ecommerce and SaaS lists churn quickly, so re-check them more often. Email verification for ecommerce and SaaS covers that cadence. To compare tools side by side, see best email verification tools and our buyer's checklist for choosing a verifier.

Bottom line: Verification handles the list you have. Signup checks, segmentation and re-verification handle the list you keep adding to.

What are the most common mistakes?

Bottom line: Most zero-bounce failures come from process gaps, such as unlogged codes, stale results and unverified sends, not from the verifier itself.

How we compared (and limitations)

This guide is based on public documentation: RFC 3463 for enhanced status codes, RFC 5321 for SMTP behaviour, Amazon SES's published documentation, Google's sender guidelines and the FTC's CAN-SPAM guide. We have not run controlled tests against any verifier, ESP or receiving provider. Nothing here is a measured result from Unlimited Verifier beyond its published plan facts.

Unlimited Verifier's 99.5% figure is the company's stated accuracy for deep verification, not an independent benchmark. The worked example (84,000 Valid, the 0.30% and 5.0% residual rates, and the 627-bounce total) uses illustrative assumptions. Replace them with your own first-wave measurements. Thresholds vary by provider and change without notice.

Bottom line: Treat every figure here as a planning input to check against your own sends, not as a promise from any tool.

Worked example: what 99.5% accuracy means on 100,000 rows

If a verifier is 99.5% accurate, then 0.5% of 100,000 addresses = 500 misclassified addresses. Those errors can go either way: some bad addresses marked Valid and some good addresses marked Invalid. Measure your own bounce rate on sent Valid contacts to see the real residual risk.

Frequently asked questions

Does email verification remove all bounces?

No. Verification removes many addresses that would bounce, but it cannot remove all of them. Mailboxes can close after the check, catch-all domains accept any address, and receiving servers can reject mail based on sender reputation. Verification lowers bounce rates predictably rather than eliminating them.

What bounce rate is considered acceptable?

A commonly used target is under 1% bounces on sends to contacts marked Valid, with 2% as a ceiling. These are recommended working numbers, not universal rules, because providers do not publish identical thresholds. Measure your own rate and compare it against your ceiling.

Why do valid emails still bounce?

A valid-looking address can bounce if the mailbox was closed or filled after verification, if the server had a temporary error, or if the receiving server rejected your sending domain or IP. The verifier saw an earlier answer, not the status at send time.

What is a catch-all domain?

A catch-all domain is a mail domain configured to accept mail for any local part, even non-existent mailboxes. Because the server says yes to everything, a verifier cannot confirm whether a specific individual mailbox exists on that domain.

Should I send to Risky email addresses?

Usually not at first. Risky addresses, such as catch-all results or unclear server responses, carry more uncertainty. Hold them back, send to Valid contacts first, and only mail Risky addresses selectively after you have reviewed engagement and bounce data.

How often should I re-verify my email list?

Re-verify on a schedule that matches how quickly your list decays. Many teams re-verify before major campaigns and periodically for dormant contacts. The right cadence depends on list age, signup source and your measured bounce trend.

Does an SMTP check send an email to the address?

No. An SMTP mailbox check opens a conversation with the mail server and asks whether it would accept a recipient, typically stopping before any message body is sent. Results vary because some servers limit or hide these answers.

Can a high verifier accuracy rating guarantee deliverability?

No. An accuracy rating describes how often the verifier's prediction matches the outcome in its test conditions. Even at 99.5%, a 100,000-address list would still have about 500 misclassified addresses, and deliverability also depends on sender reputation and content.

What should I log when a message bounces?

Log the bounce type (hard or soft), the SMTP response code and text, the timestamp, and the recipient domain. Patterns such as many soft bounces to one provider can reveal reputation or throttling issues that verification alone cannot fix.

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 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.