Email bounce rate = (bounced messages / emails sent) × 100. For permission-based marketing lists, Campaign Monitor sets the benchmark at under 2% total. A hard bounce rate that consistently sits above 2% signals a list hygiene problem that mailbox providers will notice before you do.
That number is the short answer. The nuance is in what each threshold triggers and which lever to pull when you cross it.
The Bounce Rate Formula and How to Calculate It
Bounce rate has two common denominators, and your ESP may use either:
Denominator 1 — emails sent:
Bounce Rate = (Bounces ÷ Emails Sent) × 100
Denominator 2 — emails attempted (excluding pre-send suppressions):
Bounce Rate = (Bounces ÷ Emails Attempted) × 100
Most marketing platforms (Mailchimp, Campaign Monitor, Brevo) use “emails sent” as the denominator. Transactional email APIs often report against “attempted,” which excludes addresses already on your suppression list. Check your provider’s documentation to know which you’re reading.
Worked example:
You send a campaign to 10,000 addresses. Your ESP reports 85 hard bounces and 120 soft bounces.
- Hard bounce rate: (85 ÷ 10,000) × 100 = 0.85%
- Soft bounce rate: (120 ÷ 10,000) × 100 = 1.20%
- Total bounce rate: (205 ÷ 10,000) × 100 = 2.05%
That 2.05% total warrants a list review. The hard bounce figure of 0.85% is the more urgent signal — hard bounces indicate permanently invalid addresses that damage your reputation with every send.
Hard and soft bounces have different root causes and require different responses. For the full breakdown of SMTP codes, retry logic, and programmatic suppression, see Soft Bounce vs Hard Bounce: What They Are and How to Handle Them.
Bounce Rate Thresholds: What the Numbers Mean in Practice
Not all bounce types carry the same weight. The thresholds below are guidance based on published ESP documentation and industry benchmarks — your domain’s specific tolerance depends on sending volume, list age, and mailbox provider policy.
| Bounce Rate | Status | Recommended Action |
|---|---|---|
| Hard < 0.5%, Total < 2% | Healthy | Maintain list hygiene; monitor for trend changes |
| Hard 0.5–2%, Total 2–5% | Investigate | Audit recent sign-up sources; run list validation |
| Hard > 2%, Total > 5% | Urgent | Pause campaigns; clean list before next send |
Campaign Monitor puts it directly: “The benchmark for bounces is less than 2%” and notes that “if you’re seeing bounce rates over 5%, or even as high as 10% or greater, this suggests a significant problem.”
Twilio SendGrid’s documentation takes a more permissive stance, noting that “Twilio SendGrid recommends generating hard bounces from fewer than 5% of your attempted messages,” while also stating that “excessive hard bounces can negatively impact your reputation and cause deliverability problems.” The 5% figure is a ceiling before account review, not a target — 2% is the defensible threshold for healthy sending programs.
Hard vs. soft bounce thresholds differ for a reason. A single hard bounce means you sent to a permanently invalid address. Mailbox providers count these cumulatively. Soft bounces (temporary failures like full mailboxes) are less damaging when handled with proper retry logic and escalation after repeated failures.
Why Bounce Rate Is a Sender Reputation Signal
Mailbox providers do not see your list-building practices directly. What they see is your send behavior. A high hard bounce rate is interpreted as evidence that you are emailing addresses you should not have — purchased lists, scraped addresses, or an opt-in process that does not confirm validity.
The result is reputation damage at the IP and domain level. Once your reputation degrades, even messages to valid, engaged recipients start missing the inbox. High bounce rates feed into the same scoring systems that evaluate spam complaints. Google’s Gmail guidelines specify that when “messages start bouncing or start being deferred, reduce the sending volume until the SMTP error rate decreases.” Yahoo’s sender guidance explicitly lists “Monitor hard and soft bounces as well as inactive recipients” among its best practices.
The connection is direct: bounce management is one piece of the broader sender reputation picture, alongside authentication, engagement rates, and complaint rates. The full set of inbox placement factors is covered in the email deliverability best practices guide.
Soft vs. Hard Bounce Handling: The Short Version
The Soft Bounce vs Hard Bounce post covers SMTP codes and retry logic in full. For bounce-rate management, the rule-of-thumb is:
- Hard bounce: Suppress the address immediately and permanently. Count it against your rate.
- Soft bounce: Retry with exponential backoff; escalate to permanent suppression after 3-5 failures over 24-72 hours. Repeatedly soft-bouncing addresses are hard bounces in practice.
- Watch the trend, not just the snapshot. A hard bounce rate climbing month-over-month — even at low absolute values — points to a sign-up source problem. A one-campaign spike often points to a specific list segment or a broken validation step.
8 Tactics That Keep Bounce Rate Below 2%
1. Use Confirmed (Double) Opt-In
Sending a confirmation email before adding an address to your active list eliminates typos, bots, and disposable addresses at the source. Mailgun’s deliverability guidance lists double opt-in as the primary tactic for reducing bounce rates, because it verifies both that the address is syntactically real and that the person controls it. The trade-off is a smaller initial list — but a list that bounces at 0.3% outperforms a larger list that bounces at 3% on every deliverability metric.
The mechanics and conversion impact of confirmed opt-in are covered in the double opt-in guide.
2. Validate Addresses at the Point of Entry
Real-time email validation at signup catches common problems before they reach your list: syntax errors, invalid domains, disposable-address services, and role accounts (info@, noreply@). Most validation APIs return a risk score within 100ms — fast enough to embed in a signup form without user-visible friction. This is especially important for high-volume flows like free trials and content downloads where bot submissions inflate your list with invalid addresses.
3. Run Bulk Verification Before Large Sends
Addresses decay. People change jobs, abandon mailboxes, and let domains expire. A verification pass before a large campaign or reactivation sequence identifies stale addresses before they bounce, rather than letting your sending infrastructure discover them the hard way.
4. Suppress Hard Bounces Immediately
Hard-bounced addresses must go on your suppression list the moment the bounce event fires. Do not wait for end-of-campaign cleanup. Modern ESPs handle this automatically; if you manage your own suppression list or use a transactional API directly, the suppression should fire in the same webhook handler that receives the bounce event.
5. Authenticate Your Sending Domain
Authentication failures generate bounces that look like recipient problems but are actually sender problems. A 5.7.1 rejection from a receiving server often means your message failed the recipient domain’s DMARC policy check — not that the address is invalid. If you see a bounce spike from a previously clean list, check SPF, DKIM, and DMARC records before suppressing the affected addresses.
What Is Email Authentication? covers the SPF/DKIM/DMARC setup. For DMARC-specific configuration, see How to Set Up DMARC.
6. Warm Up New Sending Domains and IPs
New infrastructure has no reputation. Sending high volume from a fresh domain immediately triggers rate limiting and deferrals that inflate your apparent bounce rate and can create lasting reputation damage before your list even gets a fair read. A structured warm-up ramps volume gradually over several weeks. The email warmup guide covers the ramp schedule and common mistakes.
7. Sunset Inactive Subscribers Before They Become Bounces
Addresses that have not engaged in 6-12 months carry elevated risk of becoming invalid, being repurposed as spam traps, or generating complaints. An engagement-based sunset policy — a re-permission campaign followed by removal of non-responders — reduces bounce rate proactively. It also improves open rates and lowers complaint exposure at the same time.
8. Never Use Purchased or Scraped Lists
Lists acquired outside your own opt-in flow almost always contain invalid addresses, spam traps, and addresses that have never heard of you. Bounce rates from cold purchased lists routinely exceed 10%. Beyond the bounce rate problem, the spam complaint rates from recipients who never consented can trigger account suspension at most ESPs within a single campaign. If your bounce spike traced to a purchased list, the fix is not cleaning the list — it is discarding it.
If your bounce rate problem has already reached your inbox placement, Why Do My Emails Go to Spam? covers the diagnostic steps.
SaaS teams that want automatic hard-bounce suppression, soft-bounce retry logic, and built-in authentication without building the webhook infrastructure can explore Coldletter, which handles suppression list management as part of the sending layer.
Frequently Asked Questions
What is a good email bounce rate?
A total bounce rate below 2% is the accepted benchmark for permission-based email programs, with hard bounces ideally below 0.5%. Campaign Monitor identifies 2% as the threshold above which the rate warrants investigation, and rates above 5% as indicative of a significant problem. These are guidance figures — what matters most is the trend direction and whether the bounce source points to a specific list hygiene issue.
What causes a high email bounce rate?
The most common causes are invalid or mistyped addresses collected without confirmed opt-in, list decay on addresses not verified recently, sending to purchased or scraped lists, and authentication failures (SPF/DKIM/DMARC misconfigurations that trigger 5.7.1 rejections). A sudden spike rather than a slow climb usually points to a specific campaign source, a new sign-up form lacking validation, or a broken authentication record.
How do I lower my email bounce rate?
The highest-leverage interventions are: enabling confirmed (double) opt-in at signup, validating addresses in real time on signup forms, suppressing hard bounces immediately after each send, and auditing SPF, DKIM, and DMARC records to rule out sender-side rejections. For chronic problems, running a full list verification pass before the next send will remove most stale addresses at once.
Does bounce rate affect email deliverability?
Yes, directly. Mailbox providers treat high hard bounce rates as a signal of poor list quality. Google’s Gmail guidelines state that senders whose messages begin bouncing should reduce sending volume until the error rate decreases. Sustained high bounce rates damage IP and domain reputation, which reduces inbox placement rates across your entire sending volume — not just the bouncing campaign.
What is the difference between hard bounce rate and soft bounce rate?
Hard bounce rate counts permanent delivery failures: invalid addresses, non-existent domains, or servers that permanently refuse your messages. Soft bounce rate counts temporary failures where delivery may succeed on retry. Hard bounce rate is the more critical number because each hard bounce represents an address that should be permanently suppressed; soft bounces may resolve on their own with proper retry logic. For SMTP code definitions and handling patterns, see Soft Bounce vs Hard Bounce.
How is email bounce rate calculated?
Bounce rate = (number of bounced messages ÷ number of emails sent) × 100. Some providers use “emails attempted” (excluding pre-suppressed addresses) as the denominator instead of “emails sent.” The two produce different absolute percentages from the same underlying bounce events, so check your ESP’s documentation to confirm which denominator it applies.
Should I remove soft-bounced addresses from my list?
Not immediately. Retry soft bounces using exponential backoff, starting at 5-10 minutes and increasing with each attempt. After 3-5 failed attempts over 24-72 hours with no successful delivery, escalate the address to permanent suppression and treat it as a hard bounce. Addresses that consistently soft-bounce are unlikely to recover within the window that matters for transactional or time-sensitive email.
I’ve spent my career building software at scale with a soft spot for email: deliverability, lifecycle campaigns, and getting messages to actually land. I started Coldletter to fix what bugged me about transactional and marketing email tools. I’m based in Vancouver.
