Email Bounce Rate — What It Is, Types, and How to Reduce It
What is email bounce rate
Bounce rate is the percentage of sent emails that were returned as undeliverable. The formula is straightforward:
Bounce rate = (bounced emails / sent emails) × 100
If you send 1,000 emails and 25 come back, your bounce rate is 2.5%.
Bounce rate is one of the key metrics of email deliverability. Mail servers track it continuously and use it to adjust your sender reputation. A high bounce rate signals a low-quality recipient list — and that is a red flag for email providers.
Hard bounce vs. soft bounce
The SMTP protocol (RFC 5321) distinguishes two types of responses that result in non-delivery. They differ in severity and require different responses.
Hard bounce — permanent failure (5xx)
A hard bounce means the email cannot be delivered permanently. The sending server receives a 5xx response code — most commonly:
- 550 5.1.1 — recipient does not exist (typo in address, deleted account)
- 550 5.1.2 — recipient domain does not exist
- 550 5.7.1 — recipient refused delivery (sender blocked)
- 551 5.1.6 — mailbox has moved, no forwarding address available
Hard bounces require immediate removal of the address from your mailing list. Repeatedly sending to non-existent addresses is one of the strongest negative signals for reputation.
Soft bounce — temporary failure (4xx)
A soft bounce means the email cannot be delivered right now, but the issue may be temporary. The server returns a 4xx code:
- 450 4.2.1 — recipient mailbox is full
- 451 4.7.1 — temporary rejection (greylisting, rate limiting)
- 452 4.3.1 — insufficient storage space on the recipient server
- 421 4.7.0 — temporary connection error
The sending server typically retries delivery over 24–72 hours. If a soft bounce persists on the same address, you should remove it after 3–5 consecutive failed attempts.
Enhanced status codes (RFC 3463)
The three-digit SMTP code (e.g., 550) is supplemented by enhanced codes in the X.Y.Z format:
| Position | Meaning | Example |
|---|---|---|
| X | Category: 2 = success, 4 = temporary failure, 5 = permanent failure | 5.1.1 |
| Y | Problem area: 1 = address, 2 = mailbox, 7 = security | 5.1.1 |
| Z | Specific detail within the area | 5.1.1 |
Code 5.7.26 (RFC 7372) signals multiple authentication check failures — in practice, mail servers most commonly return it when rejecting email based on DMARC policy, where both SPF and DKIM alignment failed.
What bounce rate is acceptable
Industry benchmarks for 2026:
| Metric | Value | Rating |
|---|---|---|
| Total bounce rate | under 1% | Excellent |
| Total bounce rate | 1–2% | Acceptable |
| Total bounce rate | 2–5% | Problematic — needs attention |
| Total bounce rate | over 5% | Critical — risk of blocking |
| Hard bounce rate | under 0.5% | Target value |
| Soft bounce rate | under 1% | Normal range |
Industry consensus and email provider guidelines agree on the 2% threshold. Repeatedly exceeding it leads to domain reputation degradation and increased spam filtering.
How bounce rate relates to authentication
Missing or misconfigured email authentication is one of the bounce causes that can be eliminated easily.
SPF and bounces
If you send emails from a server not listed in your SPF record, the recipient may reject the message with code 550 5.7.23 (SPF validation failed). A typical scenario:
- You deploy a new marketing tool (Mailchimp, SendGrid)
- You forget to add its servers to your SPF record
- Emails from that tool start bouncing
Check your SPF record — the analyzer verifies whether it covers all your sending servers.
DKIM and bounces
An invalid or missing DKIM signature alone rarely causes an immediate bounce. However, combined with a strict DMARC policy (p=reject), the recipient will reject emails without a valid DKIM signature — resulting in a hard bounce.
DMARC and bounces
DMARC with p=reject policy instructs recipients to reject emails that fail authentication outright. If neither your SPF nor DKIM passes alignment checks, the result is a bounce with code 5.7.26.
Domains with full authentication (SPF + DKIM + DMARC) are 2.7 times more likely to reach the recipient's inbox compared to unauthenticated domains, according to industry data.
How to reduce bounce rate
1. Maintain a clean recipient list
- Remove hard bounces immediately — after the first permanent failure, remove the address from your list
- Monitor soft bounces — deactivate addresses after 3–5 consecutive failed delivery attempts
- Verify addresses at collection — double opt-in confirms that the address exists and the recipient actually owns it
- Clean inactive contacts regularly — move recipients who haven't opened an email in 6–12 months to a re-engagement segment or remove them
2. Set up complete authentication
Without SPF, DKIM, and DMARC, you risk bounces caused by recipient-side rejection:
- Your SPF record must cover all servers you send from
- Your DKIM signature must be valid and the key in DNS must not be expired
- Set up a DMARC record with at least
p=noneand a reporting address
v=DMARC1; p=none; rua=mailto:example.com@rua.spfmonitor.com,mailto:dmarc@example.com
DMARC reports reveal which of your emails fail authentication — and may therefore bounce.
3. Monitor SMTP responses
Analyze the bounce codes you receive. Each code points to a specific cause:
| Code | Cause | Solution |
|---|---|---|
| 550 5.1.1 | Non-existent address | Remove from list |
| 550 5.7.1 | Sender blocked | Check blacklists |
| 550 5.7.23 | SPF failure | Update SPF record |
| 550 5.7.26 | DMARC failure | Fix SPF/DKIM alignment |
| 452 4.3.1 | Insufficient storage | Wait and retry |
4. Monitor blacklists
Getting your IP address or domain on a blacklist causes widespread email rejection. Regularly check the most commonly used blacklists — Spamhaus, Barracuda, SORBS.
5. Increase volume gradually
When switching to a new IP address or provider, follow proper IP warmup procedures. A sudden spike in sending volume leads to temporary bounces because the recipient server doesn't yet recognize the new IP.
How to measure bounce rate
Most email platforms (Mailchimp, SendGrid, Amazon SES) display bounce rate directly in their dashboards. For a more comprehensive view, combine multiple data sources:
- DMARC reports — show authentication results for each sending IP address. Set up report collection and review them regularly.
- Google Postmaster Tools — displays domain reputation, complaint rates, and authentication results for Gmail.
- SMTP logs — for precise diagnostics of specific bounce codes.
Bounce rate is just a number — what matters is understanding the causes behind it. A hard bounce on a non-existent address requires a different response than a bounce caused by DMARC authentication failure.
