An email bounce rate is the percentage of the messages you send that fail to be delivered and are rejected by the receiving mail server. You calculate it by dividing the number of bounced messages by the number of messages sent, then multiplying by 100. A healthy bounce rate sits under 2 percent, and the best-kept lists run below 1 percent.
Every bounce is the receiving server telling you it could not, or would not, accept your message. A small number of bounces is normal even with perfect hygiene, because people change jobs and abandon mailboxes. The problem is not the occasional bounce. It is a rate that climbs high enough to tell mailbox providers your list is stale, poorly sourced, or built without permission. That is when your reputation and your inbox placement start to slide.
The formula itself is simple: bounce rate = bounces / sent * 100. The nuance is in what kind of bounces you are counting and what you do about each one, which is where the rest of this guide lives.
Not all bounces are equal. A hard bounce is a permanent failure you must suppress on the first occurrence. A soft bounce is temporary and worth retrying. Treating the two the same way is the most common mistake senders make, and it quietly wrecks reputations.
What happens when an email bounces
When delivery fails, the receiving server returns a rejection along with a Non-Delivery Report and an SMTP status code that explains why. Your sending system reads that code to decide whether to retry the message or give up and suppress the address for good.
Think of every send as a request that the receiving server can accept, defer, or refuse. If the address is valid and nothing is wrong, the message is accepted and moves toward the inbox. If something temporary is in the way, the server defers and your system retries for a while. If the address is permanently unreachable, the server refuses outright and there is nothing more to try.
Message sent
The receiving server inspects the address and your sending signals.
Accepted
The address is valid. The message is delivered toward the inbox.
Soft bounce
A temporary 4xx error. Your server retries for a few days.
Hard bounce
A permanent 5xx error. Suppress the address immediately.
Hard bounce vs soft bounce
A hard bounce is a permanent failure: the address will never accept mail, so you remove it at once. A soft bounce is a temporary failure: the address is fine, but something blocked delivery this time, so you retry and only suppress it if the failures persist.
Hard bounces
A hard bounce means delivery can never succeed at that address. The receiving server answers with a 5xx code, signalling a permanent condition. Typical reasons are an address that does not exist (a typo, a fake signup, or a closed account), a domain with no mail servers, or a sender that the recipient has permanently blocked. Hard bounces are the most damaging type, because sending to addresses that do not exist is exactly what spammers do when they blast unverified lists.
Soft bounces
A soft bounce means the address is real but delivery failed for a temporary reason. The server answers with a 4xx code and your system retries on a schedule, often for up to four or five days. Common causes are a full mailbox, a server that is briefly down or overloaded, a message that is too large, rate limiting, greylisting, or a temporary content-based block. A single soft bounce is harmless. The same address soft bouncing across several consecutive sends should be treated as a hard bounce and suppressed.
| Factor | Hard bounce | Soft bounce |
|---|---|---|
| Nature | Permanent failure | Temporary failure |
| SMTP class | 5xx (for example 5.1.1) | 4xx (for example 4.2.2) |
| Typical cause | Invalid address, no such domain, sender blocked | Full mailbox, server busy, rate limited, greylisting |
| Recoverable | No, the address is dead | Yes, often delivers on retry |
| What to do | Suppress on the first bounce | Retry, then suppress after repeated failures |
| Reputation impact | Severe and immediate | Low, unless it persists |
Set a soft-bounce threshold and let your system enforce it automatically. A common rule is to suppress any address that soft bounces on three to five consecutive campaigns. That captures abandoned mailboxes before they harden into hard bounces and spam traps.
How to read a bounce code
Bounce messages carry two numbers: a basic SMTP reply (such as 550) and an enhanced status code in the format class.subject.detail (such as 5.1.1), defined in RFC 3463. The first digit is what matters most: a 5 means permanent, a 4 means temporary.
The enhanced code is the precise reason. The leading digit mirrors the basic reply, the middle number groups the problem (addressing, mailbox, network, policy, and so on), and the final number narrows it down. Once you can read the first digit you can route every bounce correctly, even before you read the human-language explanation that usually follows.
| Code | Type | Meaning |
|---|---|---|
5.1.1 | Hard | User unknown, the mailbox does not exist |
5.1.2 | Hard | The domain has no mail servers or does not resolve |
5.7.1 | Hard | Message refused by policy, the sender is blocked |
4.2.2 | Soft | Mailbox is full, try again later |
4.7.1 | Soft | Greylisted or rate limited, retry shortly |
Servers do not always follow the standard perfectly, so the text in the bounce message is worth reading when a code looks ambiguous. For a code-by-code reference, search the full bounce code library for the exact 5.x.x or 4.x.x value you received, or read the companion guide to email bounce codes for the patterns behind them.
What counts as a good bounce rate?
Keep your total bounce rate under 2 percent, and treat under 1 percent as the target for a well-maintained, permission-based list. Hard bounces alone should stay below roughly 0.5 percent. Once your rate climbs past 5 percent you are in danger of throttling, filtering, and account suspension.
Use these bands to judge where you stand and what the number is telling you:
| Total bounce rate | What it means | What to do |
|---|---|---|
| Under 1% | Excellent, a clean and engaged list | Maintain your current hygiene |
| 1% to 2% | Acceptable, normal for an active list | Keep cleaning and watch the trend |
| 2% to 5% | Warning zone, hygiene is slipping | Audit your sources and clean now |
| Above 5% | Critical, providers will react | Stop, run a full list audit, then rebuild |
Context matters when you read these numbers. Transactional mail such as receipts and password resets usually bounces less than marketing mail, because the addresses were active moments earlier. A first send to an older list will bounce more than a regular send to people who hear from you often. Judge yourself against your own trend line as much as the benchmark, and investigate any sudden jump.
What causes email bounces
Bounces come down to two things: addresses that cannot receive mail, and conditions that block mail this time. The first group creates hard bounces and almost always traces back to list quality. The second creates soft bounces and is usually temporary.
Why hard bounces happen
- The address does not exist. A typo at signup, a fabricated address, or an employee who left and had their mailbox closed.
- The domain cannot receive mail. The domain is misspelled, expired, or has no MX records, so there is nowhere to deliver.
- You have been blocked. The recipient or their provider has placed a permanent block on your sending domain or IP.
- Purchased or scraped data. Bought lists are full of dead addresses and spam traps that bounce the moment you send.
Why soft bounces happen
- The mailbox is full. A common and genuinely temporary condition that often clears on its own.
- The server is busy or down. Brief outages, maintenance, or overload on the receiving side.
- Rate limiting or greylisting. The provider is deliberately slowing an unfamiliar sender and asking you to try again.
- The message is too large or filtered. An oversized message or a content-based block bounces for that send only.
How to reduce your bounce rate
Lowering your bounce rate is about stopping bad addresses at the door and removing the ones that go stale. Validate before an address ever joins your list, confirm intent, and let automation suppress failures the moment they happen.
Validate addresses at signup
Add real-time validation to every form: check the format, confirm the domain has MX records, catch common typos like gmial.com, and optionally block disposable domains. Most bad addresses can be stopped before they ever enter your list.
Use confirmed opt-in
Require new subscribers to click a confirmation link before they are added. Confirmed (double) opt-in is the single most effective way to keep typos, bots, and fake addresses out of your list and your hard bounce rate near zero.
Suppress hard bounces immediately
Configure your platform to remove any hard-bounced address on the first failure and store it on a permanent suppression list, so it can never be mailed or re-added by accident.
Retry soft bounces, then sunset them
Let soft bounces retry over a day or two. If the same address fails on three to five consecutive sends, suppress it. Persistent soft bounces are usually abandoned mailboxes on their way to becoming hard bounces.
Re-engage or remove inactive subscribers
Subscribers who have not opened or clicked in six to twelve months are likely drifting toward abandoned or recycled accounts. Run a re-engagement campaign and remove anyone who does not respond before they start bouncing or hit a spam trap.
Monitor bounces by source and provider
Track bounce rates per acquisition source and per mailbox provider. A single source with high bounces points to a bad form or data problem; a spike at one provider often means you have been blocked there.
Never keep mailing an address after it hard bounces, and never send to a purchased list. Repeated sends to dead addresses are read as spammer behavior and can land you on a blacklist within a single campaign. Suppress on the first hard bounce, every time.
How bounces hurt your sender reputation
Mailbox providers watch your bounce rate as a direct proxy for list quality, and high bounces drag down the reputation that decides whether your mail reaches the inbox. The damage compounds, because a weaker reputation means more filtering, less engagement, and an even worse reputation.
The mechanics are straightforward. Sending to invalid addresses is the clearest sign of a list that was bought, scraped, or never cleaned, so providers like Gmail, Outlook, and Yahoo fold your bounce rate into their reputation scoring. A sustained high hard bounce rate is also one of the strongest triggers for landing on a blacklist, and your email platform monitors the same number, with most enforcing thresholds in the 2 to 5 percent range before they throttle or suspend an account.
Left unchecked, this becomes a downward spiral: high bounces lower your reputation, lower reputation pushes more mail to spam, spam placement cuts engagement, and falling engagement pushes your reputation lower still. Keeping bounces low is one of the cheapest, highest-leverage things you can do to protect inbox placement. To see how your bounces sit alongside authentication, blacklist status, and DNS, run a free Sender Reputation Checker, and read what sender reputation is for the full picture.