Article

What Bounce Rate Gets an ESP Account Suspended? Thresholds and Fixes

By Unlimited Verifier Team ·

Diagram of ESP bounce rate thresholds showing a 2% safe zone, the 5% review line, and the 10% pause line for email account suspension.

Summary

Amazon SES's documentation cites 5% bounce rate for an account review and 10% for a pause, while most other ESPs publish no fixed figure. Because enforcement is discretionary, a safe planning ceiling is under 2% total bounces per campaign. Small sends are especially risky, since a few bad addresses can push the percentage over a threshold.

The published benchmark is 5% for an account review and 10% for a pause. Amazon SES's documentation cites both figures, while the public documentation we reviewed for most other ESPs gives no fixed number. Plan around a stricter ceiling of under 2% total bounces per campaign.

This article covers which bounces count, how the rate is calculated, and what to do at each level. For the broader picture of why suspensions happen, read our pillar guide on high bounce rate account suspension.

Quick answer

What bounce rate gets an ESP account suspended?

The published figures are few, and the real trigger is a judgment call. Amazon SES's documentation describes 5% as a level that may place an account under review, and 10% as one that may pause sending. Other platforms enforce at their discretion and can act on a single campaign.

Platform Published figure What it means in practice Our planning number
Amazon SES 5% review, 10% pause Documented, so you can cite it in an appeal Under 2%
Most other ESPs (e.g., Mailchimp, SendGrid, Brevo, Mailgun) No fixed public figure we could confirm Notice wording and account history decide Under 2%, and act on any warning immediately

Platform-specific notices are covered in our guides to Mailchimp suspensions, SendGrid review notices, Brevo suspensions and Mailgun warnings.

Why so strict? Many customers share sending IP addresses and domains. One customer's dead list damages reputation for everyone on the same pool, so an ESP often acts before mailbox providers do. A threshold is a review trigger, not a verdict. Reviewers also weigh complaints, spam-trap hits and your account history.

Bottom line: Treat 5% and 10% as the outer edge of risk, not as a target.

How is an ESP bounce rate calculated, and why does segment size matter?

A bounce rate is only as meaningful as the division behind it. Most campaign reports divide bounces by emails sent, but confirm your ESP's exact formula, because two dashboards can show the same count and different rates.

Small segments are where accounts get caught. At 400 contacts, 5% is 20 bounces. If 22 of 400 bounce, the rate is 22 ÷ 400 = 5.5%, above SES's review line, even though 22 addresses sounds minor. The same number of bad addresses in a 40,000-contact send would produce a much smaller percentage. A test segment built from one bad import file can cross a threshold on its own, even when the full list is healthy.

Timing matters too. Hard bounces usually come back quickly, but soft bounces and delayed bounce notices can arrive hours later. A figure read in the first few minutes understates the final number, so wait for the report to settle before you judge a campaign.

Bottom line: Calculate the rate on the segment the platform will judge, and treat small segments as higher risk.

Which bounces count toward the rate?

Bounce type is set by the SMTP enhanced status code in the rejection. RFC 3463 defines the classes: a 5.x.x code is a permanent failure (hard), and a 4.x.x code is temporary (soft). The second digit indicates the subject.

Code Class Usual meaning Counts toward your ceiling?
5.1.1 Hard Bad destination mailbox (address doesn't exist) Yes
5.1.2 Hard Bad destination system (domain problem) Yes
4.2.2 Soft Mailbox full Only if it repeats across sends
5.7.1 Hard, policy-based Delivery not authorized, message refused Yes, but suppressing these addresses won't fix the cause

The 5.7.x rejections are the trap. They're often driven by your sending reputation or the recipient's policy rather than a dead address. Removing those addresses tidies your list without fixing the problem, so investigate your sender reputation when you see them.

Our rule: count hard bounces plus any soft bounce that repeats on three or more sends. A full mailbox today may be fine next month. An address that soft-bounces across three campaigns is effectively dead.

Bottom line: Hard bounces and repeat soft bounces make up your real rate.

Can complaints get you suspended before bounces do?

Yes, and complaints are the most under-discussed risk. Google's sender guidelines ask bulk senders to keep spam rates below 0.10% and to avoid reaching 0.30%, as measured in Google Postmaster Tools. Yahoo's sender requirements set a similar complaint ceiling of 0.3%.

The arithmetic is tight. On 10,000 delivered emails, 0.3% is 30 complaints and 0.1% is 10. In our view, a 0.4% complaint rate is more urgent than a 1% bounce rate on a well-verified list, because complaints feed directly into mailbox-provider filtering. Bounces and complaints often share a root cause: recipients who never expected to hear from you.

Bottom line: Track complaints per 1,000 delivered alongside bounces, and investigate at 1 per 1,000.

Can a low bounce rate still get you suspended?

Yes. A bounce rate is a lagging indicator of list quality, and it can't show spam-trap hits or blacklist listings. Recycled spam traps are addresses abandoned long enough that a provider reactivates them to catch senders who don't clean lists. They typically accept the message rather than bouncing it, so your bounce count stays flat while your reputation drops.

Check the sending domain separately. Unlimited Verifier offers a free domain blacklist checker that shows whether a domain is listed, which is a quick test to run alongside your bounce report. If a campaign shows a low bounce rate but a sudden drop in inbox placement, check blacklists before you assume the list is fine. For what a single bad campaign does to deliverability over time, see does one high-bounce campaign hurt deliverability for weeks.

Bottom line: Watch bounces, complaints and blacklist status together, because each can fail without the others moving.

Which sending patterns push bounce rates over the line?

For SaaS and ecommerce teams, the risky patterns are predictable.

Sending pattern Bounce risk Why What to do
Engaged contacts, confirmed within 90 days Low Recent confirmation means current addresses Monitor per campaign
Trade-show or event import, never verified High Typos, unclear consent, job changes Verify before the first send, and segment
Dormant list (no sends in 12+ months) High Addresses churn and get abandoned Re-verify, suppress, reconfirm
Migration without suppression history High The old platform's bounce data is lost Import your own suppression file first
Public signup form without validation Medium to high Typos and bots Real-time validation at capture
Purchased or scraped lists Very high No consent, and spam traps are common Don't send; recovery is hardest here

Migration risk is covered in our guide to bounces after switching email providers, and the reactivation playbook is in how to send to an old email list safely.

Bottom line: The riskiest sends are the ones that skipped verification at entry.

What should you do at each bounce rate level?

Apply these bands to hard bounces plus repeat soft bounces per campaign. The bands are our recommendation, built on the 2% ceiling and the published SES lines.

Bounce rate (per campaign) Interpretation Immediate action
Under 1% Healthy Keep sending; log the rate
1% to 2% Watch Find the responsible segment; verify it before the next send
2% to 5% Over our ceiling Pause that segment; verify and suppress; write up the cause
5% to 10% At or above the SES review line Pause sends to affected lists; contact the ESP
Over 10% At or above the SES pause line Stop sending; follow the reinstatement path

If you've just seen a spike, the five steps after a bounce rate spike list gives the immediate sequence. For a sudden jump with unclear causes, see what to do when your bounce rate suddenly spikes.

Bottom line: The band tells you how urgent the response is, and the segment tells you what to fix.

How do you calculate your bounce rate the way an ESP would?

  1. Open the campaign report. Note emails sent, delivered, hard bounces and soft bounces.
  2. Calculate the hard-bounce rate. Hard bounces ÷ sent × 100. For example, 36 ÷ 1,200 × 100 = 3.0%.
  3. Add repeat soft bounces. Export your bounce log and count addresses with soft bounces on three or more sends. Suppose that adds 14. Total: 50 ÷ 1,200 × 100 = 4.2%.
  4. Calculate the complaint rate. Complaints ÷ delivered × 100.
  5. Compare the result with the band table above.
  6. Log the figures with the date, campaign name and segment, so you can spot trends across sends.

Bottom line: Your ESP's number is the result; the next section shows how to predict it before you send.

Hands-on: predict your bounce rate before you send

This is the procedure for estimating how many addresses in a list will bounce before you mail it.

  1. Export the list as a CSV from your ESP or CRM, including the email column and an engagement or source field if you have one.
  2. Create an account if you don't have one. You can sign up on the Free plan and upgrade if your list is larger.
  3. Upload the file. Go to Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically.
  4. Let the verification run. Each address is checked for syntax, domain, MX records and the SMTP mailbox, and catch-all, disposable and role-based addresses are flagged.
  5. Read the three buckets. Valid addresses are safe for the first send. Invalid addresses are the ones that would bounce. Risky addresses include catch-all domains, which accept any address, so the mailbox can't be confirmed.
  6. Estimate the bounce rate. Invalid count ÷ total × 100. If the result is above 2%, don't send the full list.
  7. Suppress Invalid addresses in your ESP, re-import the Valid contacts as a new segment, and hold Risky contacts until the main list has shown a stable rate.
  8. Export your results as CSV, Excel or JSON and keep the summary counts. You'll need them if you ever have to explain a bounce spike.

To spot-check a single address before it goes into a segment, the free email checker runs the same kind of check on one address at a time.

Bottom line: Verify, estimate, suppress, then send; the estimate is what keeps the live rate under your ceiling.

Worked example: predicting an 18,400-contact import

A B2B SaaS team imports 18,400 trade-show contacts and plans a first send to the full list. This example is illustrative. The plan limits and arithmetic are real, and the verification results are hypothetical.

Choosing a plan. The Free plan allows 25 lists of up to 150 emails a month, which caps uploads at 25 × 150 = 3,750 emails, and it includes 750 deep verifications. That isn't enough for 18,400. The Pro plan ($29 a month, or $25 a month billed annually) accepts lists of up to 25,000 emails and includes 25,000 deep verifications a month, so the whole import fits in one list.

Cost. At monthly billing, $29 ÷ 18,400 × 1,000 ≈ $1.58 per 1,000 contacts. At annual billing, $25 ÷ 18,400 × 1,000 ≈ $1.36 per 1,000. Standard verification is included on every plan, so there are no per-email fees. For context on how verification is priced across vendors, see email verification pricing.

Hypothetical results:

What the arithmetic says:

The company states 99.5% accuracy for deep verification. That is Unlimited Verifier's own figure, not an independent benchmark, so monitor the first send anyway. Verification turns a predicted 7% bounce into a list you can send with a measured rate.

Bottom line: One Pro month and a short upload turn a predicted 7% bounce rate into a Valid audience you can measure.

Which list-hygiene method keeps bounces under the line?

Method What it catches What it misses Best use
Suppress known bounces only Addresses that already failed Every untested address Baseline only
Sunset by inactivity (e.g., no opens in 12 months) Long-dormant contacts Recent bad entries from forms or imports Policy, not proof
Bulk verification Syntax, domain, MX, mailbox, catch-all, disposable and role flags Consent and engagement Pre-send gate for every list
Real-time validation at capture Typos and bad domains before entry Addresses that go bad later Ongoing prevention

When you compare best email verification tools, check whether results are categorized clearly enough to act on, whether you can export them in a format your team uses, and whether the tool supports the cadence you need. Our buyer's checklist for choosing a verifier covers these in detail.

Bottom line: Only verification gives you a pre-send estimate; the other methods tidy up history.

How do you keep bounces under 2% over time?

  1. Verify at capture. Add real-time validation to forms. For single addresses or bulk batches, use the email verification API. Batches go up to 10,000 emails per request, and Pro includes 100,000 API emails a month. See email verification API and automation for workflow patterns. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so connect through the API or use the export-verify-re-import workflow.
  2. Verify every import before the first send. Split files so each one fits your plan's list limit.
  3. Send to recent engagers first. A new list sent to the most engaged segment keeps early bounce rates low.
  4. Confirm auto-suppression is on. Hard bounces and repeat soft bounces should drop out of future sends automatically.
  5. Set alerts. Flag any campaign above 1% and review anything above 2%.
  6. Re-verify on a schedule. Monthly for active B2B lists and quarterly for others is a reasonable starting point. Verification supports email verification compliance and hygiene, but it can't prove consent, so keep your own opt-in records. Free plan results are kept for 24 hours and Pro for 30 days, so export and store the reports you may need later. The full cadence is in our list maintenance best practices guide.

Bottom line: Consistent gates at capture, import and send do more than any single cleanup.

Common mistakes that push accounts over the line

Bottom line: Most suspensions come from ignoring an early warning, not from one bad campaign.

How we compared (and limitations)

This article is based on public documentation: Amazon SES's published thresholds, RFC 3463, Google and Yahoo sender guidelines, and Google Postmaster Tools. We haven't tested how any ESP enforces its thresholds, and platform rules change without notice, so check your provider's current policy. Where sources disagree or stay silent, we recommend the stricter 2% ceiling. Unlimited Verifier figures come from its published plan details, and the 99.5% deep-verification accuracy is the company's stated figure. Worked-example percentages and results are hypothetical.

Small-segment bounce math

Contacts Bounces Bounce rate Vs. SES 5% review line
400 20 5.0% At the review line
400 22 5.5% Above the review line
40,000 22 0.055% Far below the line
40,000 2,000 5.0% At the review line

Takeaway: the same 22 bad addresses are a near-certain problem in a 400-contact test segment and almost invisible in a 40,000-contact send. Verify small segments before every send.

Frequently asked questions

Is there an official bounce rate that gets you suspended?

Not for most providers. Amazon SES's documentation cites 5% as a level that may trigger review and 10% as one that may pause sending. Most other ESPs publish no fixed number and decide case by case, so account history and complaints also matter.

What is a safe bounce rate for email marketing?

Plan to keep total bounces under 2% per campaign, and aim for under 1% on newly imported or re-engaged lists. Staying well below published review lines gives you a buffer against sudden spikes and against discretionary enforcement.

How do you calculate email bounce rate?

Divide the number of bounced emails by the number of emails sent, then multiply by 100. For example, 22 bounces out of 400 sent is 5.5%. Confirm your ESP's formula, since some dashboards report slightly different denominators.

Why does list size affect bounce rate risk?

Each bad address counts the same, so a small segment has a much larger percentage per bad address. Twenty bounces is 5% of 400 contacts but only 0.05% of 40,000. A single bad import file can push a small test send over a threshold.

Do hard and soft bounces count the same?

They are usually both counted in total bounce rate, but they signal different problems. Hard bounces, such as nonexistent addresses, are the more serious sign of list hygiene issues. Soft bounces, such as a full mailbox, are often temporary but still contribute to totals if retried repeatedly.

Can spam complaints suspend an account even with a low bounce rate?

Yes. Google asks bulk senders to keep spam rates below 0.10% and to avoid reaching 0.30%. A clean bounce rate does not protect you if complaints are high, and reviewers weigh complaints heavily.

What should I do if my ESP sends a bounce rate warning?

Pause sends to the affected list, identify the source of invalid addresses, and remove hard bounces immediately. Then verify the remaining list before resuming, and respond to the notice with a clear description of the corrective steps you took.

How do I lower bounce rate before sending?

Verify addresses with a list-validation service, remove invalid and role-based addresses, suppress previous hard bounces, and avoid importing purchased or scraped lists. Re-check new imports before the first send to a segment.

Does a bounce rate threshold apply to every ESP the same way?

No. Amazon SES publishes specific figures, while providers such as Mailchimp, SendGrid, Brevo and Mailgun generally do not publish a fixed suspension threshold. Their notices and enforcement depend on context, so read each platform's warning carefully.

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.