You're halfway through a campaign, the copy is approved, the segments are ready, and the dashboard suddenly shows a pile of rejected messages. Six hundred bounces from twelve thousand sends feels alarming, but the number alone doesn't tell you whether the problem is a decaying newsletter list, a risky cold-outbound database, or a temporary receiving-server issue. To understand bounce rates in email, you need to separate the metric itself from the reasons behind it, then interpret it according to the type of program you're running.
Table of Contents
- What Bounce Rates Email Really Measure
- Hard Bounces and Soft Bounces Explained
- How to Calculate Your Email Bounce Rate
- Bounce Rate Benchmarks by Program Type
- Why Bounce Rate Affects Deliverability and Reputation
- Step-by-Step Ways to Lower Your Bounce Rate
- Verifying Lists With CleanMyList Before You Send
- Monitoring Bounce Rates as an Ongoing Habit
What Bounce Rates Email Really Measure
A bounce is an email that the receiving mail system refuses to accept or deliver. The sender's email platform usually receives a non-delivery report, then records that failed attempt in the campaign results. In simple terms, the bounce rate is the share of attempted messages that came back rejected.
The basic relationship looks like this:
Bounce rate = bounced emails ÷ emails sent × 100
That calculation sounds straightforward, but email platforms can label the underlying events differently. “Sent” generally means the platform attempted delivery. “Delivered” may mean the receiving server accepted the message, not that the message reached the recipient's primary inbox. Some systems report delivery based on acceptance at the SMTP stage, while others use their own reporting rules.
That distinction matters. A server can accept an email and still route it to junk, place it behind a security gateway, or filter it before the recipient sees it. The difference between delivery and inbox placement is one of the most important ideas in email deliverability.
The denominator changes the story
Suppose a campaign sends to twelve thousand addresses and six hundred are rejected. Using sends as the denominator produces a different result from a report that calculates failures against accepted or delivered messages. Your ESP's help documentation should tell you which formula it uses.
A campaign-level rate gives you a snapshot of one send. A rolling rate combines several campaigns and helps reveal whether list quality is improving or deteriorating. Both views are useful, but they answer different questions.
Practical rule: Treat the bounce rate as a diagnostic signal, not a final verdict on campaign health.
Program type, list age, acquisition source, and sending channel all influence the result. A permission-based newsletter with recent sign-ups behaves differently from a cold-outbound campaign built from older business contacts. Transactional mail has another operating context because it's usually triggered by a customer action and often targets addresses that were recently used.
Hard Bounces and Soft Bounces Explained
Email platforms classify failures primarily by whether the delivery problem appears permanent or temporary. The distinction determines what you should do next.
A hard bounce is a permanent rejection. The address may not exist, the recipient account may have closed, or the receiving domain may no longer accept mail. SMTP responses such as 550, 5.1.1, and user unknown commonly indicate that the recipient can't be delivered to under the stated address.
Think of a hard bounce as knocking on a shop that has permanently closed. Trying again won't solve the problem. Suppress the address immediately, preserve the record for compliance and customer-history purposes, and prevent future marketing sends to it.
A soft bounce is a temporary failure. The mailbox may be full, the receiving server may be greylisting or throttling traffic, the message may be too large, or the provider may be experiencing a short outage. This is like arriving at a locked shop during business hours. A later attempt may succeed.
Match the response to the failure
Your ESP may retry soft bounces automatically. Check how its retry policy works, then watch repeated failures rather than treating every temporary rejection as harmless. An address that fails across two or three sending cycles deserves re-verification or a controlled re-engagement decision.
Common soft-bounce messages include mailbox-full responses, “try again later” responses, and message-size rejections. The exact wording varies by provider, so review the SMTP response and the mailbox domain together.
| Attribute | Hard Bounce | Soft Bounce |
|---|---|---|
| Meaning | Permanent delivery failure | Temporary delivery failure |
| Typical causes | Invalid address, closed mailbox, nonexistent recipient | Full mailbox, greylisting, throttling, short outage, oversized message |
| Common response codes | 550, 5.1.1, user unknown | Mailbox full, try again later, message too large |
| Recommended action | Suppress immediately | Retry according to policy, then investigate repetition |
| Future sending | Don't send again unless the recipient provides a corrected address | Resume only if later delivery succeeds |
| Risk signal | Strong evidence of list decay or bad acquisition data | Possible operational, provider, or data-quality issue |
Hard bounces deserve the strictest treatment because the failed address is unlikely to become deliverable without a correction. Soft bounces require judgment. A one-time mailbox-full response isn't equivalent to a nonexistent address, but repeated soft failures can reveal an abandoned or unhealthy contact.
How to Calculate Your Email Bounce Rate
A campaign sends 15,000 messages, and 315 return as bounces. The standard calculation is:
Bounced emails ÷ emails sent × 100
Using those figures:
315 ÷ 15,000 × 100 = 2.1%
The non-bounce portion is 97.9% at that reporting level. That percentage means the platform did not record those messages as bounced. It does not confirm delivery to the primary inbox, since accepted messages may still be filtered into spam or another folder.
Why ESP reports can differ
Email service providers may use different denominators. One platform may calculate bounce rate from attempted sends, while another may use a delivered-base metric or exclude certain events through its processing rules. The displayed percentage can therefore change even when the number of rejected emails remains the same.
Record the raw totals beside the reported rate:
- Attempted sends, the messages the platform tried to deliver.
- Hard bounces, permanent failures that should drive suppression.
- Soft bounces, temporary failures requiring follow-up.
- Accepted messages, which show receiving-server acceptance.
- Inbox placement, measured separately through seed testing or provider-specific monitoring.
A seed-based inbox test sends messages to controlled addresses at selected mailbox providers. It can show whether a message appears in the inbox, spam folder, or another filtered location. Keep this result separate from bounce-rate calculation. A pre-send email list check can reduce invalid-recipient risk, but it cannot prove that every accepted message reaches the primary inbox.
Use bounce data to evaluate recipient validity, and placement testing to evaluate filtering. Each measures a different part of delivery.
Bounce Rate Benchmarks by Program Type
A newsletter may reject an address because a subscriber record has gone stale. A cold-outbound sequence may include an address gathered with less certainty. A transactional message is triggered by a customer event and should be judged against that event and the recipient's activity. These programs produce different bounce-rate baselines, so one universal “good” rate can mislead.
For permission-based email marketing, Validity's global benchmark reported an average bounce rate of approximately 1.5% in 2022, implying roughly 98.5% delivery at the ESP-reporting level. The same benchmark placed global average inbox placement just below 85%. A sender can therefore see a low rejection rate while messages still fail to reach the primary inbox. The Validity benchmark summary provides that global context.
Well-managed programs often aim lower. Twilio describes hard bounces under 0.5% and soft bounces under 1% as usual targets, with 2% or higher as a warning zone. Treat these figures as starting points, then account for list source, audience behavior, and program type. The Twilio's email marketing benchmark report documents those benchmark thresholds.
Three programs, three interpretations
| Program Type | Typical Bounce Rate | Healthy Target | When to Act |
|---|---|---|---|
| Permission-based newsletter | Often near the global 1% to 2% baseline | Hard bounces below 0.5%, soft bounces below 1% | Investigate sustained totals at 2% or higher, especially when hard bounces rise |
| Cold outbound | Can sit higher because older or less certain addresses are common | Keep hard bounces as low as possible and verify before sending | Review targeting, sourcing, and verification when failures remain persistent |
| Transactional email | Should be judged against address activity and the event that triggered the message | Protect valid customer communication and suppress permanent failures quickly | Investigate provider-specific spikes, authentication issues, and repeated temporary failures |
| High-churn verticals | May fluctuate as addresses change or become inactive | Separate hard and soft results instead of relying on one total | Segment by source, age, provider, and event type before changing the whole program |
Cold-email comparisons need particular care. A 2025 report put average hard bounces at 2.48% industry-wide, while a 2026 cold-email dataset reported a 2.2% blended bounce rate across more than 53 million sends, and another benchmark estimated 1.71% across 7.5 million emails. These studies cover different populations and methods, so they provide context rather than a target. The comparison appears in BillionVerify's deliverability report.
For every program, separate hard and soft bounces before interpreting the total. The combined rate can conceal permanent list decay or a temporary receiving problem. A newsletter, outbound sequence, and transactional stream may show similar percentages while requiring completely different actions.
Why Bounce Rate Affects Deliverability and Reputation
A campaign can show a low bounce rate and still miss the inbox. Mailbox providers evaluate delivery failures as signals of how carefully a sender manages recipient data. Repeated attempts to reach nonexistent addresses may indicate weak acquisition controls, aging records, or sending without meaningful permission. Those patterns can lead to throttling, blocking, or stronger spam filtering.
Hard bounces need prompt action because the destination is permanently unavailable. Mailing those addresses again provides no audience value and shows that suppression rules are not working. Soft bounces require context. A sudden cluster at one provider may reflect throttling, infrastructure trouble, reputation issues, or an outage on the receiving side.
Accepted isn't the same as visible
“Delivered” often means only that the receiving server accepted the message. It may still enter spam, pass through a security gateway, sit in quarantine, or be filtered before the recipient sees it. A global benchmark cited earlier illustrates the gap between a low bounce rate and actual inbox placement. A permission-based program can avoid many rejected messages while still losing visibility in the inbox.
A low bounce rate proves that fewer messages were rejected. It doesn't prove that more messages reached the primary inbox.
Use bounce results alongside complaint rates, opens, clicks, unsubscribes, spam-trap signals, and seed-based placement tests. Break the analysis down by mailbox provider and program type. A newsletter, cold outbound sequence, and transactional stream can post similar bounce percentages while pointing to different risks and requiring different responses.
The goal is not zero bounces at any cost. Maintain a permissioned, current list, remove permanent failures quickly, investigate concentrated soft-bounce patterns, and protect the sender reputation that helps wanted messages reach recipients. A clean list is one input to deliverability, not proof of inbox placement.
Step-by-Step Ways to Lower Your Bounce Rate
Bounce prevention begins at signup, not after the ESP reports a failure. Build the workflow so bad addresses are challenged, classified, or suppressed before they enter a major campaign.
-
Control acquisition quality. Use confirmed opt-in where appropriate, identify the sender clearly, and keep marketing consent separate from unrelated registrations. Don't buy lists, append contacts without permission, or assume an event registration authorizes every future promotion.
-
Validate the form input. Catch obvious spelling mistakes and reject malformed addresses at entry. Store first name, last name, and email in separate fields, and keep country information outside the email address itself.
-
Verify immediately before sending. Classify new and aging records as invalid, disposable, role-based, catch-all, spam-trap, syntax-error, or unknown. Upload only the segment your policy allows, and keep the rejected records outside the campaign audience.
-
Apply suppression rules consistently. Hard bounces, unsubscribes, and global suppressions should never re-enter a send through a second list or an outdated CRM export. A separate suppression process is especially important when several teams use different sending tools.
Inspect the send, not just the list
After each campaign, compare verification outcomes with actual ESP results. If soft bounces cluster at one provider, inspect retry behavior, sending pace, message size, and authentication before deleting a broad segment.
For dormant records, choose between a re-engagement path and a sunset policy. Repeatedly mailing contacts that haven't interacted gives you little useful signal and keeps aging data in circulation.
Teams looking for a broader operational checklist can review these bounce rate reduction strategies from Quikly, then adapt the recommendations to their consent model and ESP rules. The important part is consistency: verify imported data, maintain suppression lists, and schedule re-checks for records that have aged since their last validation.
Verifying Lists With CleanMyList Before You Send
A verification pass is most useful when every result leads to a defined action. CleanMyList groups addresses into eight verdict categories: valid, invalid, role-based, disposable, spam-trap, catch-all, syntax-error, and unknown. Each category helps determine whether to send, suppress, or investigate.
The workflow is simple:
- Upload a CSV or paste the addresses.
- Review the dashboard's verdict breakdown.
- Filter records by risk category.
- Create send, suppress, and re-engagement segments.
- Export only the approved segment to your email platform.
The service checks address syntax, DNS, SMTP mailbox existence, catch-all behavior, disposable providers, role accounts, historical bounce reputation, and a final send-or-skip recommendation. It doesn't send messages during verification, which keeps the process separate from the campaign itself. The CleanMyList verification workflow explains how the upload and result stages fit together.
Read the verdicts as decisions
Consider a 10,000-row file with this result:
- Valid: 6,850
- Invalid: 740
- Disposable: 410
- Role-based: 280
- Catch-all: 150
- Spam-trap hits: 120
- Syntax errors: 90
- Unknown: 1,360
The figures total the original file, so you can reconcile the dashboard before exporting. Send the valid segment according to your permission and program rules. Suppress invalid addresses, syntax errors, spam-trap hits, and disposable records when your policy excludes temporary mailboxes.
Role-based addresses such as shared departmental inboxes need a policy decision. For a personal newsletter, they may be poor engagement candidates. For a business notification, they may have a legitimate operational purpose. Spam-trap hits deserve priority suppression because mailing them can expose a serious acquisition or list-maintenance problem.
Catch-all and unknown records need more caution. A catch-all domain may accept mail for addresses that haven't been confirmed, while an unknown result can reflect insufficient evidence rather than a definite failure. Keep those rows in a review or re-engagement segment instead of treating them as automatically valid.
Monitoring Bounce Rates as an Ongoing Habit
List cleaning isn't a one-time repair. Addresses change, mailboxes close, domains alter their policies, and acquisition sources introduce new risks. A sender can finish one clean campaign and still develop a bounce problem if the underlying process remains unchanged.
Use a quarterly review to keep the system accountable:
- Review bounce logs by type. Separate hard failures from temporary responses, then inspect the underlying SMTP reasons.
- Audit acquisition sources. Compare form, import, event, partner, and outbound segments rather than blending them.
- Compare with the right baseline. Judge each program against its own history and the relevant newsletter, outbound, or transactional context.
- Re-verify aging records. Put the full database on a 90-day review rotation when your list volume and risk profile justify it.
- Check suppression lists. Confirm that hard bounces and unsubscribes remain excluded across every sending system.
- Document infrastructure changes. Record migrations to a new ESP, domain, or sending setup so you can connect timing with any performance shift.
Know when to pause
Some signals need action before the normal review cycle. A single send with more than 5% hard bounces, any spam-trap hit, a sudden complaint-rate increase, or a post-migration spike should trigger an immediate pause. The 5% hard-bounce warning threshold is an operational rule for triage, not a universal industry benchmark.
During the first hour, stop the affected campaign, suppress the offending cohort, and run a targeted verification pass. Don't resume just because a later retry produces fewer failures. Identify whether the source, provider, data import, or sending change caused the anomaly.
CleanMyList helps marketers verify CSV files or pasted addresses across eight signals, separate sendable contacts from risky records, and export a cleaner audience before a campaign begins. Visit CleanMyList to check your next list, review the verdicts, and reduce avoidable bounce risk before you hit send.