Article
What Bounce Rate to Expect After Email Verification
By Unlimited Verifier Team ·

Summary
A list sent with only Valid addresses should typically bounce under 1%, and roughly 1-2% once Risky addresses such as catch-all domains are included. Bounces above 3% after verification usually mean something was missed upstream or the data aged between the check and the send.A fully verified list sent with only Valid addresses should typically bounce under 1%, and 2% is the safe planning ceiling for a mixed list that includes catch-all domains and natural decay. These are planning ranges, not published industry benchmarks. If you still see 3% or more after verifying, something was missed upstream, or the data aged between the check and the send.
Quick answer
- Valid-only sends: plan for under 1% hard bounces, and aim for about 0.5% on contacts verified in the last 30 days.
- Valid plus Risky: expect roughly 1–2%, because catch-all and disposable addresses hold most of the residual risk.
- Unverified purchased or dormant lists: bounce rates can easily exceed 5% (an illustrative range, not a benchmark), so verification should cut them sharply.
- Your ceiling: keep total hard bounces under 2%. Platforms publish different thresholds, and some act earlier than others, so this single number gives you a margin.
What bounce rate should you expect after email verification?
Expect about 0.2–1% hard bounces on Valid-only sends, and plan for roughly 1–2% once Risky addresses are included. The exact figure depends on three variables: how recently you verified, how many catch-all domains the list contains, and how many calls the verifier got wrong. Public sources don't publish a consistent post-verification bounce figure, so replace these ranges with your own measured numbers after the first send.
Verification is not a guarantee. It removes addresses that are dead at the moment of checking. It cannot remove the ones that die next week, or the ones on servers that accept everything.
The outer limits come from mailbox providers and ESPs. Amazon SES's documentation describes bounce-rate reviews starting at 5% and possible pauses at 10%. Google's sender guidance focuses on spam complaints rather than bounces. Your working target should sit well inside those limits.
Bottom line: Plan for under 1% on Valid-only sends, and treat anything above 2% as evidence that something was missed upstream.
Why does a verified list still bounce?
A verified list bounces because verification is a snapshot of a system that keeps changing. Four things create the residual bounces.
- Decay after the check. People change jobs, mailboxes close and domains lapse. The gap between verifying and sending is itself a bounce variable.
- Catch-all domains. A catch-all server accepts mail for any address at that domain, so the verifier cannot confirm the specific mailbox exists. This is why verifiers have a Risky bucket at all.
- Wrong calls. No verifier is perfect. Some addresses marked Valid will hard-bounce, and some marked Invalid are actually deliverable. The second error costs list size; the first costs reputation.
- Lookalike domains with live mail servers. A misspelled domain can have working MX records if someone has registered it, so domain-level checks pass it. The SMTP mailbox check and engagement history catch these more reliably.
For why verifiers disagree on these edge cases, see why different email verifiers give different results and what a false positive is in email verification.
Bottom line: Residual bounces come from time, catch-all domains and imperfect calls. You can shrink all three, but none reaches zero.
How do you calculate the bounce rate to expect?
Use a weighted segment formula: multiply each segment's expected bounce rate by the number of addresses sent to it, add the results, and divide by the total sent.
Expected bounce rate = (Σ sent × segment bounce rate) ÷ total sent
A blended number hides the segment causing trouble. A list that is 90% clean and 10% catch-all can average out acceptably while the catch-all group produces most of the bounces. Plug in the planning rates below, then swap in your measured numbers after your first send.
| Segment | Planning bounce rate (illustrative) | Why it differs |
|---|---|---|
| Valid, verified in the last 30 days | 0.2–0.5% | Little time for decay; mailbox confirmed |
| Valid, verified 30–90 days ago | 0.5–1.5% | Decay has had time to act |
| Valid, verified over 90 days ago | Re-verify first | Decay estimates become unreliable |
| Risky, catch-all domains | 3–10% | Mailbox never confirmed; depends on the receiving provider |
| Risky, disposable or role addresses | Measure before sending | Disposable addresses are often short-lived; role accounts often reach shared inboxes |
| Invalid | Remove, do not send | Known to fail |
Bottom line: Calculate by segment, not by list. The formula shows where a bounce problem will come from before you press send.
Which verification checks predict bounces?
The SMTP mailbox check removes most dead addresses on non-catch-all domains. Catch-all and disposable flags tell you where the leftover risk sits.
| Check | What it catches | What it misses | Bounce risk left behind |
|---|---|---|---|
| Syntax | Missing @, illegal characters, double dots | Well-formed addresses that don't exist | Low on its own; mostly a pre-filter |
| Domain and MX | Nonexistent domains and domains with no mail server | Working domains with a nonexistent mailbox | Moderate; lookalike domains often pass |
| SMTP mailbox | Most nonexistent mailboxes on non-catch-all servers | Catch-all domains, which accept everything | Low on non-catch-all domains |
| Catch-all detection | Domains that accept any address | Whether the specific mailbox exists | Unresolved; this is what Risky is for |
| Disposable and role flags | Temporary inbox services; shared addresses such as info@ | Real personal mailboxes | More an engagement risk than a bounce risk |
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox, detects catch-all domains, and flags disposable and role-based addresses. Results sort into Valid, Risky and Invalid, which map onto the table above. When you compare best email verification tools, ask which of these layers each one reports separately and which it rolls into a single score.
For what a Valid result does and doesn't promise, read does a valid result mean the email will be delivered.
Bottom line: A Valid result means the mailbox passed the checks at that moment. It does not mean the person still reads mail.
What bounce rate is normal for each type of list?
Your list's origin sets the target more than any universal benchmark does. The table uses planning assumptions, because published benchmarks for this exact comparison are scarce.
| List scenario | Typical bounce rate before cleaning (illustrative) | Expected after verifying Valid only |
|---|---|---|
| Own opt-in signups, active in last 90 days | 0.5–1.5% | Under 0.5% |
| Own list, dormant 12+ months | 2–5% | 0.5–1.5% after re-verifying |
| Trade-show or purchased leads | 5–15% | 0.5–1.5%, with Risky held back |
| Legacy CRM import after a platform migration | 3–8% | 0.5–1% once suppression history is merged |
For teams running email verification for ecommerce and SaaS, the biggest gap is between lists you collected and lists you were given. A collected list has engagement history to check against. A purchased list has none, so verification becomes your only evidence.
Bottom line: Set the target by origin. Purchased and dormant lists need stricter treatment than opt-in lists.
How do you measure post-verification bounces correctly?
Measure hard bounces per attempted send, within a fixed window after each send. Most measurement errors come from the wrong numerator or denominator.
- Denominator: attempted sends. Suppressed addresses shouldn't count. Otherwise a list you already cleaned looks cleaner than it is.
- Numerator: 5.x.x codes only. RFC 3463 defines enhanced status codes whose first digit gives the class: 2 is success, 4 is transient, 5 is permanent. A code such as 5.1.1 (bad destination mailbox) is a hard bounce. Track 4.x.x separately as a deliverability signal, because those may succeed on retry.
- Window: a fixed 48–72 hours. This is a practitioner convention, not a published standard. Read the number at the same point after every send so comparisons hold.
- Segment: track the rate by the same segments you used in your formula.
Before you trust a verifier's buckets on your own list, test a sample first. How many emails to use when testing a verifier covers how to size that test.
Bottom line: Use attempted sends as the denominator, count only hard bounces, and read the number at a fixed point.
Worked example: a 50,000-contact list before and after verification
This example is illustrative. The arithmetic and plan limits are real; the bucket results and bounce rates are assumed for teaching.
The situation. A company has 50,000 contacts, mostly from older trade-show imports and a legacy CRM, and is about to send a product update.
Plan limits that shape the job. On the Free plan, you get 25 lists a month of up to 150 emails each. That caps a month at 25 × 150 = 3,750 addresses, so a 50,000-row list does not fit. On Pro ($29/month, or $25/month billed annually), each list holds up to 25,000 emails, so the file splits into two uploads of 25,000. Standard verification is unlimited on every plan, and Pro includes 25,000 deep verifications a month. See email verification pricing for how the plans compare.
Path A: send the raw list. Suppose 2,500 addresses are dead.
2,500 ÷ 50,000 = 5.0% hard bounce rate
That sits exactly at the 5% level that Amazon SES's documentation describes as a review trigger, before any bounces from catch-all addresses are counted.
Path B: verify, then send in segments. Use deep verification on the oldest imports, where decay risk is highest. Results (illustrative):
| Bucket | Count | Share |
|---|---|---|
| Valid | 41,000 | 82% |
| Risky (catch-all 5,000; disposable or role 1,500) | 6,500 | 13% |
| Invalid | 2,500 | 5% |
Check: 41,000 + 6,500 + 2,500 = 50,000.
Step 1: send Valid only. Assume 0.4% of Valid addresses bounce, from decay and wrong calls combined:
41,000 × 0.4% = 164 bounces 164 ÷ 41,000 = 0.40%
Step 2: see what adding Risky does. Assume the Risky group bounces at 6%:
6,500 × 6% = 390 bounces (164 + 390) ÷ (41,000 + 6,500) = 554 ÷ 47,500 = 1.17%
Adding the Risky group nearly triples the blended rate, from 0.40% to 1.17%. That gap is the reason the first send should go to Valid addresses only. Test the Risky group separately.
Bottom line: Raw list 5.0%, Valid-only 0.40%, mixed 1.17%. The decision about the Risky bucket moves the result more than anything else in the process.
How do you run a verification pass that keeps bounces low?
Follow these steps before every large send. For a 50,000-row list, the work takes an afternoon.
- Export the list from your ESP or CRM as a CSV. Include the email column and engagement fields such as last open or last purchase date.
- Remove known problems first. Suppress unsubscribes, spam complaints and prior hard bounces. Export your ESP's suppression list too, because it doesn't carry over automatically when you change platforms.
- Upload and verify. Go to upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. On Pro, split any list over 25,000 rows first. To test the workflow on a small file, you can sign up for free.
- Read the three buckets. Valid is safe for the first send. Risky needs a separate decision. Invalid goes out of your list.
- Export and save the counts as CSV, Excel or JSON. Results on the Free plan are kept for 24 hours and on Pro for 30 days, so save your bucket counts before they expire. You will need them as denominators later.
- Send Valid only for the first campaign, starting with the most recently engaged contacts.
- Test Risky separately. Catch-all addresses belong in a small test send, not a full one. The catch-all email verification page explains how these results are handled.
- Suppress Invalid permanently in your ESP, then re-import Valid contacts as a new segment.
- Measure 5.x.x hard bounces per segment for 48–72 hours, using the formula above.
Unlimited Verifier has no native ESP, CRM or Zapier integration, so the basic loop is export, verify, re-import. To automate it, use the email verification API and automation pattern. API access is included on Pro (100,000 emails a month), and the API supports single-email checks and bulk batches of up to 10,000 emails per request. Generate keys on the Email verification API page.
For a quick check on one address before it goes into a campaign, use the free email checker. For ongoing practice, see real-time email validation and email list maintenance best practices. If you're weighing vendors, how to choose an email verifier lays out the criteria.
Bottom line: Verify, split by bucket, send Valid first, and measure each segment. The process keeps the number low, not the verifier alone.
Does the 99.5% accuracy figure tell you your bounce rate?
No. Accuracy describes how often individual calls are right. Your bounce rate depends on which calls were wrong and how old the data is. Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark.
Here is the arithmetic. On a 50,000-address list, 0.5% of addresses is 250. If all 250 were false Valid calls, they would add 0.5% to your bounce rate before decay or catch-all effects. In practice, errors split between false Valid and false Invalid, and only the false-Valid share hurts deliverability.
For the broader picture, read the email verifier accuracy guide and how accurate email verification really is. To judge accuracy claims, see are vendor accuracy claims for email verifiers trustworthy and do email verifiers really have 99% accuracy. For a method you can run yourself, see the independent email verifier accuracy benchmark.
Bottom line: Use accuracy to judge the verifier, and use segment bounce rates to judge the send.
Which thresholds should you trust?
Trust the most conservative credible figure. The sources measure different things and don't agree on when to act, so use one working ceiling.
- Hard bounces: Amazon SES's documentation describes review at 5% and possible pause at 10%. Some platforms act earlier on a single campaign, and they don't all publish the same number. Our recommendation: under 1% on Valid-only sends, and under 2% overall.
- Spam complaints: Google's sender guidance asks bulk senders to keep user-reported spam below 0.10% and never let it reach 0.30%. Yahoo's sender requirements set complaint expectations at similar levels, so check their current page for exact figures. Our recommendation: under 0.1%.
Verification fixes bounces. It does not fix complaints, which come from people who never wanted the mail. M3AAWG publishes sender best practices that address this distinction. The FTC's CAN-SPAM compliance guide sets the US baseline for consent and opt-out duties. Verification supports email verification compliance and hygiene, but it does not replace opt-in records.
Bottom line: Verification controls bounces. Consent controls complaints. You need both to stay under the thresholds.
Why did my bounce rate stay high after verifying?
A high rate after verification is almost always a process gap. Check these causes in order.
- Sent before verifying. A new import, form signup or CRM sync added addresses after the verification pass.
- Risky addresses included. Catch-all and disposable segments were in the send. Recalculate without them.
- Stale verification. The pass is older than about 30 days, a rule of thumb for how fast decay adds up. Re-verify and resend to the affected segment.
- A high Unknown share. Unknowns can mean the verifier could not get a clear answer from the receiving server. Why does my verifier return so many unknowns explains the usual reasons.
- Microsoft 365 domains. Some corporate domains respond differently to SMTP checks. See how accurate verifiers are on Microsoft 365 addresses.
- Suppression history lost. The list was exported and re-imported without the bounce suppressions your previous platform had applied.
- Persistent bounces in clean segments. If Valid-only sends still bounce high, check your sending domain against blacklists with the free domain blacklist checker.
Bottom line: Work through the list in order. Most high rates trace back to a segment that was sent before it was verified or never verified at all.
What mistakes inflate post-verification bounce rates?
Most inflated rates come from segmentation and timing errors, not from the verifier.
- Averaging across segments, which hides the catch-all group that causes the damage.
- Counting soft bounces as hard bounces, which sends you chasing a transient problem, or ignoring 5.x.x codes because they look like a deliverability issue.
- Using the raw list as the denominator after suppressing contacts, which makes results look worse than they are.
- Treating Risky as Valid to hit a list-size target.
- Assuming a verified list stays verified. Decay continues every week after the check.
- Losing suppression history when you export or migrate.
- Quoting a vendor accuracy figure as a bounce guarantee. Accuracy and bounce rate measure different things.
- Confusing complaints with bounces. A clean list can still generate complaints if consent is weak.
Bottom line: Keep Risky out of the first send, keep the denominator honest, and re-verify on a schedule.
How we compared (and limitations)
This article is based on public documentation: Amazon SES's published thresholds, Google and Yahoo's sender guidelines, and the SMTP enhanced status code definitions in RFC 3463. We have not run controlled tests against any ESP's review process. The bounce rates in the tables and the worked example are illustrative planning assumptions, not measured results.
Unlimited Verifier's features and limits come from its published plan details. Its 99.5% accuracy figure for deep verification is the company's own statement. The company also publishes an open-source verification engine on GitHub (github.com/unlimitedverifier/free-email-verifier), which lets you inspect the approach, though that does not independently verify the hosted service's results. Thresholds and review processes vary by provider and change over time, so confirm current numbers in each platform's documentation before a large send.
Bottom line: Use the thresholds as guardrails, and use your own segment measurements as the truth.
Planning bounce ranges by list type
| List type | Planning hard bounce range | Action |
|---|---|---|
| Valid-only, verified in last 30 days | Under 1% (aim ~0.5%) | Send normally |
| Valid plus Risky | Roughly 1-2% | Segment Risky, watch closely |
| Unverified purchased or dormant | Often above 5% (illustrative) | Verify before any send |
| Any send | Keep under 2% total | Investigate if 3% or more |
Frequently asked questions
What is a good bounce rate after email verification?
A good bounce rate after email verification is under 1% for Valid-only sends. Plan for roughly 1-2% when Risky addresses are included, and treat anything above 2% as a signal that something was missed upstream. These are planning ranges, not published industry benchmarks.
Why is my bounce rate still high after verifying?
High bounce rates after verifying usually come from data aging between the check and the send, catch-all domains that accept any address, or verifier errors. Re-verify contacts older than 30 days and review how Risky addresses were handled before sending.
Should I send to Risky addresses after verification?
Sending to Risky addresses adds bounce risk, mostly from catch-all and disposable domains. Many senders segment Risky contacts and mail them separately with lower volume, while watching hard bounces and complaints closely before expanding.
What bounce rate does Amazon SES allow?
Amazon SES documentation describes bounce-rate reviews starting at 5% and possible sending pauses at 10%. Check the current SES docs, since policies can change, and keep your own target well inside these limits.
Is a hard bounce different from a soft bounce?
Yes. A hard bounce is a permanent failure, such as a nonexistent mailbox, and should be removed from your list. A soft bounce is temporary, such as a full mailbox, and may succeed on retry. Verification mainly reduces hard bounces.
How often should I re-verify my email list?
Re-verify contacts before major sends, and treat addresses verified more than 30 days ago as aging. Lists that go unused for long periods decay faster, so re-checking dormant contacts before reactivation campaigns is especially important.
Does email verification guarantee zero bounces?
No. Verification removes addresses that are dead at the time of checking, but it cannot predict mailboxes closing next week or confirm specific mailboxes on catch-all servers. Some residual bounces are expected.
What is a catch-all domain in email verification?
A catch-all domain is a mail server configured to accept mail for any address at that domain. Verifiers cannot confirm whether a specific mailbox exists there, so these addresses usually land in the Risky bucket rather than Valid.
What bounce rate should trigger an investigation?
Most senders should investigate when hard bounces reach 2% on a send, using 3% or more as a clear signal that verification missed something. Review list source, verification age and the Risky segment before the next campaign.
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.