TLDR: A hard bounce is a permanent delivery failure, and you should stop sending to that address. A soft bounce is temporary, like a full mailbox or a server that’s busy, and it usually resolves on retry. Keep total bounces under 2% and hard bounces under 1%. Then there’s authentication rejections, where a valid address bounces after your domain fails SPF, DKIM, or DMARC.
Every bounce is an email that comes back marked “return to sender.” Your ESP counts them, labels them hard or soft, and usually handles the rest automatically.
Most of the time, that’s fine. Bad addresses get suppressed, temporary failures get retried, and your list stays reasonably clean. The system is working like it’s supposed to.
Well, until it doesn’t.
Some hard bounces mean the address is gone forever. Others mean the address is perfectly good and the receiving server rejected you. Those are two very different problems, and if you try to treat them the same way, you’ll delete real subscribers to solve a DNS problem.
First, let’s learn the difference between hard bounces vs. soft bounces, then we can break down how to fix each one.
What is an email bounce?
An email bounce happens when a message can’t be delivered and the receiving mail server sends back a rejection notice. That notice includes a status code explaining what went wrong.
Your bounce rate is the percentage of sent emails that bounced. Bounces come in two main types, hard and soft, and they need very different handling.
What is a hard bounce?
A hard bounce is a permanent delivery failure. That means it’s not going to resolve itself on its own. The most common cause is an address that doesn’t exist, whether it was mistyped at signup, belonged to someone who left their job, or was never real.
These are email addresses you do not want on your email list.
Keep sending to hard-bounced addresses and mailbox providers start to see you as a sender with a sloppy list. That drags down your sender reputation and hurts inbox placement for everyone else on it.
What is a soft bounce?
A soft bounce is a temporary failure. The address exists, but the message couldn’t be delivered right now due to a few reasons:
- Full mailbox
- Server outage
- ESP throttling (or rate limiting)
Most ESPs retry soft bounces automatically for a few days. Occasional soft bounces happen. They’re completely normal. But an address that soft-bounces campaign after campaign is often an abandoned mailbox, and it’s usually just a step away from becoming a hard bounce.
Hard bounce vs. soft bounce
Hard bounces are about the address, while soft bounces are more about the moment. Hard bounces will never fix themselves, while soft bounces sometimes (and often) do.
| Hard bounce | Soft bounce | |
| What it means | Permanent failure | Temporary failure |
| Status code | Starts with 5 (5xx) | Starts with 4 (4xx) |
| Common causes | Address doesn’t exist, domain doesn’t exist, permanent rejection | Mailbox full, server busy or down, message too large, rate limiting |
| What your ESP does | Suppresses the address | Retries delivery for a period of time |
| What you should do | Stop sending to it | Let retries run, suppress if it keeps bouncing |
Common bounces codes (and what they mean)
Fortunately, you don’t have to guess what your bounces mean. Bounce notices include enhanced status codes, defined in RFC 3463. The first digit tells you hard or soft, and the rest tells you why.
| Code | Type | What it means | What to do |
| 550 5.1.1 | Hard | Recipient address doesn’t exist | Suppress the address |
| 550 5.1.2 | Hard | Recipient domain doesn’t exist | Suppress the address, check for typos at signup |
| 552 5.2.2 | Soft | Mailbox full | Let retries run, suppress if it repeats |
| 421 4.7.0 | Soft | Temporary rejection, often rate limiting or reputation | Slow down, check sending volume and reputation |
| 550 5.7.26 | Hard (policy) | Gmail rejected the message for failing DMARC | Fix authentication, don’t suppress the address |
| 550 5.7.515 | Hard (policy) | Microsoft rejected the message for failing authentication requirements | Fix authentication, don’t suppress the address |
The bounces that aren’t bounces (fix this immediately)
Gmail, Yahoo, and Microsoft require bulk senders to authenticate their email with SPF, DKIM, and DMARC. When a message fails those checks, they reject it with a 5.7.x policy code.
A lot of ESPs file those rejections under hard bounces, and some suppress the address automatically. That means your perfectly valid subscriber gets removed from your list, and they didn’t do anything wrong. Nope, it was an email authentication problem on your end.
This tends to show up suddenly. A new sending tool goes live without proper authentication, or someone edits a DNS record, and overnight a chunk of your list starts bouncing. Every new platform that sends as your brand is another door into your domain, and one that isn’t configured correctly can accidentally turn good addresses into bounces.
How to spot it:
- Bounces spike across many addresses at once, especially at one mailbox provider
- The codes start with 5.7 (policy) rather than 5.1 (address)
- The bounces trace back to one sending platform or one recent change
If you see that pattern, fix authentication before you touch your list. The usual culprit is a sending platform that isn’t signing with your domain, or one whose authentication doesn’t align with your From address.
Once that’s corrected, the same addresses deliver normally.
While getting your email authentication right fixes bounces, that’s just the beginning. It also protects your brand (and customers) from email impersonation and phishing, and it’s the gateway to getting your logo in the inbox next to your messages.
What’s a good email bounce rate?
Open rate and click rate are calculated on delivered email, but bounces by definition weren’t delivered, so bounce rate is calculated on sent email:
Bounce rate = (Bounced emails ÷ Emails sent) × 100
Track hard and soft bounces separately, too. A 1.5% bounce rate that’s mostly soft bounces is a very different situation from a 1.5% hard bounce rate.
General benchmarks:
- Total bounce rate under 2% is a healthy threshold
- Hard bounce rate under 1%, and ideally well under it
- Typical hard bounce rates for permission-based lists land around 0.4% to 0.6%
Really, don’t worry too much about the benchmarks. Sure, you want it somewhere below 1-2%, but then compare against your own history. You’re looking for spikes and sudden changes—those indicate that you need to potentially adjust your policy or suppress addresses on your list.
ESPs watch bounce rates closely, and they might restrict or suspend accounts that run consistently high. That’s a good enough reason to stay on top of this before it becomes a problem.
How to fix hard bounces
- Check the code first. A 5.1.x code means a bad address. A 5.7.x code usually means a policy or authentication rejection.
- Suppress bad addresses immediately. Real hard bounces (5.1.1, 5.1.2) should never get another send. Remove them from your list.
- Don’t suppress policy rejections automatically. If a valid address bounced with a 5.7.x code, fix the underlying problem and keep the subscriber.
- Look for patterns. Hard bounces clustered around one signup form, import, or acquisition source point to a data quality problem at the source.
How to fix soft bounces
- Let retries run. Most soft bounces resolve on their own within a day or two. That’s normal.
- Set a repeat rule. Suppress an address after three consecutive soft bounces across separate campaigns.
- Watch for clusters by provider. If soft bounces spike at one mailbox provider while others look normal, you’re likely being rate-limited or filtered there. That’s a reputation signal. Your list is probably fine.
- Slow down if you’re throttled. Rate-limiting codes (often 421) mean you sent too much, too fast. Spread volume out and ramp up gradually.
How to reduce your bounce rate
- Use double opt-in. Confirming addresses at signup filters out typos and fake entries before they ever reach a campaign.
- Validate addresses at the point of capture. Real-time validation on signup forms catches obvious errors immediately.
- Clean your list on a schedule. Email lists decay steadily as people change jobs and abandon accounts. It happens. Remove inactive and invalid addresses regularly. It’s one of the few email marketing best practices that improves every campaign at once.
- Never buy lists. Purchased and scraped lists are full of invalid addresses and spam traps.
- Re-engage before old lists go stale. If you haven’t emailed a segment in months, verify it before sending a full campaign.
- Authenticate every sending service. SPF, DKIM, and DMARC should be configured for every platform that sends as your domain, so policy rejections never mislabel good subscribers.
- Warm up new domains and IPs. Sudden volume from an unfamiliar source triggers throttling. Increase gradually.
Keep the good addresses, lose the bad ones
Bounce management is mostly automatic…until it isn’t. This isn’t something that needs to consume your marketing or IT team every day (or even every week), but when there’s a spike, it’s time to start doing some investing.
Look for: A sudden spike, a cluster at one provider, or a wave of hard bounces from addresses that weren’t a problem before.
Valimail Monitor is free and shows every service sending email as your domain, along with whether each one is passing authentication. It’s the fastest way to catch the configuration problems behind a bounce spike. Check your domain to see where you stand.
Frequently asked questions
Should I delete hard bounce emails?
Yes, if the bounce code shows the address is invalid (5.1.x codes, like 550 5.1.1). Remove or suppress those addresses right away. Continuing to send to them damages your sender reputation. Check the code first, though. Policy rejections (5.7.x codes) usually mean an authentication problem on your side, and the address itself may be perfectly fine.
What is an acceptable hard bounce rate?
Keep hard bounces under 1% of sent email, and ideally well below that. Typical permission-based lists see hard bounce rates around 0.4% to 0.6%. A hard bounce rate climbing above 1% usually points to list quality issues, old segments, or a problematic signup source.
Why am I getting bounced emails that I didn’t send?
That’s called backscatter. It usually means someone is sending email using your domain without permission, and the bounce notices for their messages are coming back to you. DMARC at enforcement tells receiving servers to reject unauthenticated mail claiming to be from your domain, and DMARC reporting shows you who’s sending as you.
Do bounces hurt sender reputation?
Hard bounces do. Mailbox providers see repeated sends to invalid addresses as a sign of poor list hygiene, which can lower your inbox placement across your whole list. Occasional soft bounces are normal and have little effect, but persistent soft bounces at one provider can signal a reputation problem there.