Email Bounce Rate
Email bounce rate is the percentage of sent emails that fail to reach the recipient's inbox and are returned undelivered, calculated as bounces divided by emails sent.
Key takeaways
- Permanent 5xx rejections are hard bounces; temporary 4xx failures are retried as soft bounces.
- Asynchronous notifications arrive after the send, so early bounce reports understate the eventual total.
- Catch-all domains accept invalid addresses, hiding bad data behind an apparently clean rate.
- List age drives decay, because addresses expire whenever recipients change employers.
- Strict verification services occasionally reject valid addresses at unusual or self-hosted domains.
In depth
A bounce begins as an SMTP response from the receiving server. Codes in the 5xx range mean permanent rejection, so the address is retired; codes in the 4xx range mean try again later, and the sending platform queues the message for repeated attempts over a day or two. Some servers accept the message first and reject it afterwards, returning an asynchronous delivery status notification, which is why bounce counts keep rising for hours after a send completes and the first report looks clean.
Bounce rate rises with the age of the list and the looseness of the acquisition source. Addresses decay as people change jobs, so a list untouched for a year will fail far more often than one mailed weekly. Purchased or scraped data bounces hardest of all. Sending patterns matter too: a cold domain pushing large volume triggers rate limiting, which returns temporary failures that look like soft bounces. Tightening validation carries its own cost, since strict verifiers sometimes discard valid addresses at unusual domains.
Operationally the work splits between capture and pre-send. At capture, a syntax check plus an MX lookup on the domain stops most typos before the record exists; a scorecard funnel that asks for an email on the result step is a natural place to run that check, because the respondent is still on the page and can correct a mistyped address. Before each send, run the segment against a suppression list of previously bounced addresses and verify anything unmailed for several months.
A low bounce rate does not prove good delivery. Catch-all domains accept every address at the server, so junk entries never bounce and instead sit silently in the list, and a message routed to the spam folder still counts as delivered. The figure is unstable on small sends, where two failures out of eighty read as a serious problem. Providers also phrase rejections differently, so the split between hard and soft depends partly on how your platform classifies ambiguous response codes.
Example in practice
How to measure it
Split bounces by type before judging anything. Hard bounces over attempted sends is the hygiene signal, while soft bounces point at capacity, throttling or temporary outages. Then group failures by recipient domain. A rate that looks normal overall but clusters at one mailbox provider usually means a reputation problem with that provider rather than a dirty list, and the fix is different.
Track the figure by acquisition source as well, since one form or import is often responsible for most failures. Compare a segment's first send against its second: a high first-send rate points at capture quality, while a rate that climbs on later sends points at list decay. Watch the trend across campaigns rather than any single number, because one bad send tells you little.
Common mistakes
Practitioners often re-mail a long-dormant list in one large send to wake it up. The accumulated dead addresses all fail at once, the receiving provider sees a spike, and throttling follows within the same campaign. Warm up instead: mail the most recently engaged slice first, confirm the failure rate is low, then widen in stages. The second error is manually resending to soft bounces after the platform has already exhausted its own retries.
Another failure mode is deleting the bounce record along with the contact. Once the address is gone from the database, nothing stops the same person re-entering through a form and being mailed again, which restarts the cycle. Keep hard bounces in a permanent suppression list rather than erasing them. Teams also treat one global bounce figure as the whole story, when the failures are usually concentrated in a single source or domain.
Frequently asked questions
How do I reduce email bounce rate?
Validate email addresses at the point of capture, use double opt-in for new subscribers, and promptly remove hard-bounced contacts. Avoiding purchased lists and keeping your data fresh also keeps bounces low.
What counts as a high email bounce rate?
As a rule of thumb, a healthy permission-based list keeps hard bounces well under one percent of attempted sends, and anything sustained above two percent is treated as a warning sign by mailbox providers. Soft bounces run higher and vary with recipient infrastructure, so judge the two types separately rather than against one combined threshold.
What is the difference between a hard bounce and a soft bounce?
A hard bounce is a permanent rejection, usually because the mailbox does not exist or the domain is invalid, and the address should never be mailed again. A soft bounce is temporary: a full mailbox, an oversized message or a server that is briefly unavailable. Platforms retry soft bounces for a short window before converting persistent failures to hard.
Do soft bounces damage sender reputation?
Occasional soft bounces are normal and carry little weight. Repeated soft bounces to the same address across several campaigns are treated differently, because they suggest you are mailing an abandoned mailbox. Most platforms convert an address to a hard bounce after a set number of consecutive soft failures, which is the point at which it should be suppressed.
Why do valid email addresses sometimes bounce?
Greylisting is a common cause: the receiving server deliberately rejects a first attempt from an unknown sender and accepts the retry. Aggressive spam filters, message size limits and temporary outages produce the same effect. Corporate gateways also reject mail that fails authentication checks, so a missing or misaligned sending record can bounce perfectly real addresses.
How do I reduce bounce rate on a quiz or form?
Validate the field in the browser with a syntax check and a domain lookup, so an obvious typo is caught while the person is still on the page. Reject disposable-mailbox domains, and consider a confirmation step for anything entering a long nurture track. Correcting an address at the moment of capture is far cheaper than suppressing it later.
Should I remove soft bounces from my list?
Not immediately. A single soft bounce means the message could not be delivered right now, not that the address is dead. Give the platform its retry window, then flag addresses that soft-bounce on three or four consecutive campaigns and move them into a re-engagement track. Suppress them only if that track produces no opens or clicks.