Article
What to Do If 10 Percent of Your Emails Bounce: A Step-by-Step Recovery Plan
By Unlimited Verifier Team ·

Summary
If 10% of your emails bounce, pause sending to the affected list, suppress all hard bounces, and find the segment causing the failures. Verify remaining addresses and resume only with contacts that are valid and recently engaged. Treat it as an incident, since ESPs often escalate at this level.If 10% of your emails bounce, stop sending to that list, suppress every hard bounce, find the segment the failures came from, verify what remains, and resume only with addresses that verify as valid and have engaged recently. Amazon SES's public documentation describes 5% as a review threshold and says 10% can lead to a pause, so treat this as an incident, not a metric to watch.
A 10% bounce rate means one in ten messages was rejected by the recipient's mail server. ESPs read that pattern as a list-quality problem, and enforcement usually escalates from a warning to a pause. The good news is that a 10% spike is rarely spread evenly. It usually traces back to one source, which makes it fixable quickly if you work in the right order. For the wider picture of why suspensions happen, see our pillar guide on high bounce rate account suspension.
Quick answer
- Pause sending to the affected list, including automations and drip sequences, before anything else.
- Separate hard from soft bounces. Suppress hard bounces now. Hold soft bounces until you've verified those addresses or they keep failing.
- Find the segment. A 10% total often hides one source bouncing at 30–40% while the rest of the list sits near 3%.
- Verify before you resume. Send to Valid addresses first. Keep total bounces under a 2% ceiling and aim for under 1%.
What does a 10% bounce rate actually mean?
A bounce rate is bounces divided by messages sent. On a 50,000-contact send, 10% means 5,000 rejected messages. Check your platform's denominator, though. Dividing by delivered messages instead turns 10 bounces out of 100 sent into 11.1%, which can change whether you cross a threshold.
Bounces fall into two families, and they call for different responses. SMTP reply codes split into temporary (4xx) and permanent (5xx) failures, as defined in RFC 5321. The enhanced status codes in RFC 3463 add the detail you need to diagnose them.
| Enhanced code | Type | What it usually means | Action |
|---|---|---|---|
| 5.1.1 | Hard | Mailbox does not exist | Suppress now |
| 5.1.2 | Hard | Destination host not found | Suppress now |
| 5.4.4 | Hard | Domain cannot be routed, often a retired domain | Suppress now |
| 4.2.2 | Soft | Mailbox full | Retry later; suppress after repeat failures |
| 5.7.1 | Policy or reputation | Message refused by policy, block or authentication check | Diagnose the sender, not the address |
The last row is the one most teams get wrong. A 5.7.1 failure usually means the mailbox exists, but the receiving server refused your message because of your sending reputation or authentication. Deleting those addresses discards valid contacts and leaves the real problem untouched.
Sources disagree on the threshold. Amazon SES's 5% review level is the clearest public figure. Google's sender guidelines frame the risk around spam complaints instead, asking bulk senders to stay below 0.10% and never reach 0.30%. Many ESPs publish no bounce threshold at all, and enforcement can begin after a single bad campaign. We recommend a 2% total bounce ceiling and an under-1% target for the first sends after recovery.
Bottom line: A 10% rate means your list has a problem and your ESP has likely noticed. Treat it as an incident.
Why does a 10% bounce rate happen?
Most spikes are concentrated, so group bounces by source, domain, date and error code before you change anything. A blended 10% can hide one segment at 40% and everything else near 3%. The pattern tells you the cause.
| Pattern in your bounce data | Likely cause | First check |
|---|---|---|
| One source bounces at 30%+, the rest is normal | Purchased, scraped or years-old imported list | Group bounces by the source column |
| Failures cluster on one company's domain | Domain retired, or the company blocks bulk mail | Confirm the domain resolves; test one address |
| Mostly 5.7.x codes across all sources | Reputation or authentication failure | SPF, DKIM and DMARC records; blocklist check |
| Bounce rate climbing month after month | Natural decay with no sunset policy | Monthly bounce trend |
| Spike right after a signup form change | Bot or fake signups | Signup timestamps, repeated patterns, disposable domains |
| Spike right after a platform migration | Suppression and engagement history lost in transfer | Compare the new list with your old suppression file |
For B2B and SaaS lists, decay is often the main driver, because people change jobs and company domains disappear. A list that performed well two years ago can bounce heavily today. Our guide on whether a two-year-old list is safe to email covers that risk. Imports from older systems are another common trigger. See why bounce rates jump after importing a list for the pattern and how to avoid ESP suspension when importing old lists for prevention.
Bottom line: The segment breakdown decides the fix. Concentrated bounces need list surgery, while 5.7.x bounces need a sending-infrastructure fix.
What should you do in the first 24 hours?
Work through these steps in order. Each one protects the evidence you'll need later. Platform notices differ, so if you use a specific ESP, check its guide: Mailchimp, SendGrid, Brevo and Mailgun.
- Pause every sender that touches the list. Campaigns, automations and transactional flows all count. Each extra send adds bounces to the record a reviewer reads.
- Export the bounce report by error code and date, and store it outside your ESP. Suppression lists don't always migrate, and these counts will go into any appeal.
- Suppress hard bounces now. Hold soft bounces for verification. Some teams suppress an address after three consecutive soft failures. That's a common habit, not a standard.
- Break the bounces down by source, domain, date and code, using the table above.
- Check authentication and blocklists if 5.7.x codes appear. Google's guidelines require bulk senders, generally those sending about 5,000 or more messages a day to Gmail, to authenticate with SPF and DKIM and publish a DMARC policy. Check your sending domain against a blocklist checker.
- Suppress unsubscribes and complaints today. The FTC's CAN-SPAM compliance guide gives businesses 10 business days to honour opt-outs. Suppressing the same day is the safer habit.
- Verify everything that remains, including soft-bounced and unengaged contacts. The walkthrough is below.
- Write a one-paragraph cause statement and a re-entry plan. You need both whether or not your ESP asks.
Bottom line: Pause, export, suppress hard bounces, diagnose, then verify. Following this order keeps you from deleting addresses that only needed the sender fixed.
Which response option should you choose after a 10% bounce?
The options differ mainly in how much risk they remove. The main difference is whether you verify the addresses you haven't mailed yet.
| Option | What it fixes | What it misses | Repeat risk | Best when |
|---|---|---|---|---|
| A. Keep sending and let the ESP sort it out | Hard bounces the ESP already caught | Soft, dead-domain and unengaged addresses | Very high | Almost never |
| B. Suppress hard bounces only | Known failures from this send | Dead addresses you never mailed | High | Small spikes, roughly under 3% |
| C. Suppress, verify and segment | Known failures, unverified dead addresses, and low engagement | Consent gaps; sender-reputation problems | Low | A 10% spike or higher |
| D. Re-engagement send to the whole list | Some unengaged contacts | Unverified addresses, so it creates new bounces | High | Not during a review |
| E. Rebuild the list from opt-in | Consent and quality from scratch | Reach, and time | Low | Purchased or scraped lists |
Option C is the default for a 10% event. Option D is the trap. A re-engagement campaign feels like the obvious fix, but sent to unverified addresses while a reviewer is watching, it generates fresh bounces at the worst moment.
Bottom line: Use option C. Reserve option E for lists you never had consent to email.
How do you clean a list that hit 10% bounces?
If you're still shortlisting vendors, start with our roundup of best email verification tools and how to choose a verifier. This walkthrough uses Unlimited Verifier, so its plan limits decide how you split the list.
| Workflow | Best for | Limits that matter |
|---|---|---|
| Free plan, CSV upload | Small test lists and spot checks | 25 lists a month, up to 150 emails each; results kept 24 hours |
| Pro plan, CSV or Excel upload | Full-list cleaning | Lists up to 25,000 emails each; 10MB file limit; results kept 30 days |
| Pro plan, REST API | Verification at signup or import | 100,000 API emails a month; batches up to 10,000 per request |
- Export the full list from your ESP as a CSV. Include the email column, source, signup date, last-open date and bounce status. Export the bounce report as a separate file.
- Create a free account. The Free plan covers 3,750 emails a month across 25 lists of 150. A 45,000-row list would need 300 Free lists, so you'll need Pro.
- Split on Pro. Each list holds up to 25,000 emails. Save the parts as
list-1andlist-2. - Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. Confirm it was identified correctly. An email-only file of 45,000 addresses is roughly 1.2MB, so the size cap rarely binds.
- Run verification. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all domains are detected, and disposable and role-based addresses are flagged.
- Read the three buckets:
- Valid: eligible for re-entry sends.
- Risky: catch-all domains accept every address, so the mailbox can't be confirmed. Role addresses such as
info@and disposable addresses belong here too. Hold them back. The catch-all email verification page explains how these results are handled. - Invalid: suppress permanently.
- Export the results the same day as CSV, Excel or JSON. Results are kept for 24 hours on Free and 30 days on Pro, so archive them now. The counts go into your appeal.
- Re-import selectively. Add Valid contacts as a new segment, add Invalid contacts to your ESP's suppression list, and keep Risky contacts out. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so this is a manual CSV re-import or an API call from your own script.
- Spot-check edge cases with the free email checker, such as a key account that came back Risky.
Bottom line: Export, split, verify, read the buckets, archive the results, then re-import only what's valid.
What does a 10% bounce look like in practice?
The figures below are illustrative. The arithmetic and plan limits are real.
The situation. A B2B software company emailed 50,000 contacts, including a 9,000-contact trade-show import from two years earlier. The send produced 5,000 bounces:
5,000 ÷ 50,000 = 10.0% overall bounce rate
The segment split.
| Segment | Contacts | Bounces | Bounce rate |
|---|---|---|---|
| Trade-show import | 9,000 | 3,600 | 40.0% |
| Base list | 41,000 | 1,400 | 3.4% |
| Total | 50,000 | 5,000 | 10.0% |
Of the bounces, 4,100 were hard (3,300 from the import, 800 from the base) and 900 were soft (300 and 600). The base list matters most. Without the import, it still bounces at 3.4%, above the 2% ceiling. Decay affects the whole list, so all of it needs verifying.
Suppression.
- Remove 4,100 hard bounces: 50,000 − 4,100 = 45,900.
- Remove 150 unsubscribes and complaints: 45,900 − 150 = 45,750 contacts to verify.
- The 900 soft-bounced contacts stay in and get verified like everyone else.
Checking against the plan.
- Imported contacts remaining: 9,000 − 3,300 = 5,700.
- Base contacts remaining: 41,000 − 800 − 150 = 40,050.
- Split into List 1 (25,000) and List 2 (20,750), which is 45,750 in total.
- Standard verification is unlimited on Pro, so every row is covered.
- Pro includes 25,000 deep verifications a month. Spend them on the riskiest 25,000 rows: the 5,700 remaining import contacts and 19,300 base contacts with no opens in 12 months.
Illustrative results.
| Bucket | Contacts | Share | Action |
|---|---|---|---|
| Valid | 39,100 | 85.5% | Re-entry sends, in waves |
| Risky | 4,200 | 9.2% | Hold out; test later |
| Invalid | 2,450 | 5.4% | Suppress permanently |
Cost. One month on Pro is $29, or $25 a month on annual billing. Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark, so check results against your own data. For how to compare costs, see our email verification pricing overview.
Re-entry plan. Send only to Valid contacts, most engaged first. Each wave has a bounce ceiling, and the next wave waits until the current one clears it.
| Wave | Audience (Valid only) | Contacts | Bounce ceiling | Max bounces allowed |
|---|---|---|---|---|
| Day 1 | Opened in the last 30 days | 4,000 | Under 0.5% | 20 |
| Day 4 | Opened in last 90 days, not in Day 1 | 10,000 | Under 1% | 100 |
| Day 10 | Remaining engaged Valid contacts | 15,000 | Under 1% | 150 |
| Day 17 | Remaining Valid contacts | 10,100 | Under 1%, only if earlier waves held | 101 |
If Day 4 comes in at 1.4% (140 bounces on 10,000), hold the Day 10 wave, find what changed, and only then continue. The 4,200 Risky contacts stay out. Once the main list has held steady, a small test send to the best catch-all addresses is a reasonable next step.
Bottom line: The arithmetic turns a vague "we cleaned it" into a 45,750-row audit with exact counts, a $29 bill and a ramp you can defend.
How do you resume sending safely?
Resume only when the verification results are archived, Invalid contacts are suppressed and the first wave is ready. Automated warnings often clear within days of a credible response, while manual reviews commonly take several business days. Ramp over two to three weeks, and treat any wave that misses its ceiling as a reason to pause, not push on. For the mechanics of volume and pacing, see our guide to warming up a cleaned list. Inbox placement can also lag behind restored sending, which we cover in whether one high-bounce campaign hurts deliverability for weeks.
Bottom line: Ramp in waves, check each wave against its ceiling, and hold back if any wave misses.
How do you keep bounces under 2% after recovery?
Prevention matters because a recovered list can slide back in a few sends. Four habits do most of the work:
- Validate at signup with real-time validation at signup, so bad addresses never enter the list.
- Verify every import before upload. Imports are a frequent trigger, as the worked example shows.
- Re-verify on a schedule and apply a sunset rule for long-inactive contacts. The practices in list maintenance practices cover both.
- Automate if you import often. Our email verification API accepts single checks and batches of up to 10,000 emails per request, and the email verification API and automation pattern covers how teams wire this into their stack. For SaaS and ecommerce lists, email verification for ecommerce and SaaS covers how verification fits routine operations.
Bottom line: Verify at the point of entry, verify imports, and re-check on a schedule. The fourth habit is what keeps the rate from climbing back.
What mistakes make a 10% bounce worse?
- Deleting 5.7.x addresses. You lose valid contacts, and the sender-side problem remains.
- Sending a re-engagement campaign to unverified contacts. You create new bounces while the review is open.
- Suppressing only the last campaign's bounces. Dead addresses from older sends stay on the list.
- Skipping the segment breakdown. Cleaning everything at once hides the source, and the same problem returns.
- Letting results expire. Free results last 24 hours and Pro results 30 days. Export on the day you run the check.
- Treating Valid as consented. Verification confirms that an address exists, not that the person opted in. Verification supports email verification compliance and hygiene but doesn't replace opt-in.
- Re-importing Risky contacts first. They belong at the end of the ramp, if they go out at all.
- Splitting one list across several accounts to stay under sending limits. M3AAWG, an industry group, describes spreading volume this way (snowshoeing) as abusive.
Bottom line: Most failed recoveries come from sending too early or fixing the wrong problem.
How we compared (and limitations)
This guide draws on public documentation: Amazon SES's published thresholds, Google's sender guidelines, the SMTP status-code RFCs and the FTC's CAN-SPAM guidance. We have not run controlled tests against any ESP's review process, and platform thresholds change without notice, so check your platform's current notice before writing an appeal.
Unlimited Verifier's plan limits and its 99.5% deep-verification accuracy come from the company's own published figures. The accuracy figure is not an independent benchmark. The worked example uses illustrative numbers. Test a sample of your own list before relying on any verifier's results.
Bottom line: Use the thresholds here as a planning baseline, and confirm current numbers with your ESP.
Segment isolation worked example
| Source | Contacts | Bounces | Bounce rate |
|---|---|---|---|
| Website signup form | 30,000 | 900 | 3% |
| Trade show import (Mar) | 12,000 | 4,200 | 35% |
| Partner list purchase | 8,000 | 1,000 | 12.5% |
| Total | 50,000 | 6,100 | 12.2% |
Action: Suppress the trade show import and partner list entirely, verify the signup form contacts, then resume. The remaining list should sit near 3% and drop further as hard bounces are removed.
Frequently asked questions
Is a 10% bounce rate bad?
Yes. A 10% bounce rate is well above the levels most email providers accept. Amazon SES uses 5% as a review threshold and warns that 10% can lead to a pause. Treat it as an urgent list-quality problem and act before your sending account is restricted.
Should I stop sending immediately if my bounce rate is 10%?
Yes, pause sending to the affected list first, including automations and drip sequences. Continued sending to bad addresses raises your bounce rate and can trigger account suspension. Resume only after you have suppressed hard bounces and verified the remaining contacts.
What is the difference between a hard bounce and a soft bounce?
A hard bounce is a permanent failure, such as a nonexistent mailbox (5.1.1) or a domain that cannot be routed (5.4.4). A soft bounce is temporary, such as a full mailbox (4.2.2). Suppress hard bounces immediately and retry soft bounces only a limited number of times.
Should I remove soft bounces from my list?
Not immediately. Hold soft bounces and retry them over a set period. If an address keeps soft bouncing across several sends, suppress it. Removing them early can discard valid contacts whose mailboxes were only temporarily full.
How do I find which segment is causing the bounces?
Break down bounce rate by source, signup form, import date, campaign, and domain. A 10% total often hides one source bouncing at 30 to 40 percent while the rest of the list stays low. Fix or remove that source first.
Why do I see 5.7.1 bounces if the addresses are valid?
A 5.7.1 code means the receiving server refused the message on policy grounds, such as a block, reputation issue, or failed authentication. The mailbox usually exists, so deleting the address does not solve the problem. Check SPF, DKIM, DMARC, and your sending reputation.
How do I calculate bounce rate correctly?
Divide bounces by messages sent, not by delivered messages. For example, 10 bounces out of 100 sent is 10%, but dividing by 90 delivered gives 11.1%. Confirm which denominator your ESP uses before comparing against thresholds.
What bounce rate should I aim for after recovery?
Keep total bounces under a 2% ceiling and aim for under 1% on the first sends after you resume. Monitor each campaign and pause again if the rate climbs. Consistent low bounces rebuild sender trust over time.
Can I verify email addresses before sending again?
Yes. Email verification services check whether addresses are deliverable before you send. Send to addresses marked valid first, and keep unverified or risky addresses suppressed until they are confirmed or removed.
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.