Soft Bounce vs Hard Bounce: The Key Differences
A soft bounce is temporary and a hard bounce is permanent, and treating them the same quietly destroys your sender reputation. Here is what causes each and exactly what to do about them.
A bounce is the mail server's way of saying your message did not land. Two kinds matter, and they are not interchangeable. A soft bounce is temporary, the door is shut for now but might open later. A hard bounce is permanent, that address will never accept your mail. Treat them the same and you will quietly wreck your sender reputation, because the thing receiving servers punish hardest is repeatedly hammering addresses that do not exist.
The short version
Hard bounces are dead addresses: typos, closed accounts, domains that no longer resolve. Remove them immediately and never send to them again. Soft bounces are living addresses with a temporary problem: a full inbox, a server hiccup, a message that was too big. Retry those a few times, then give up if they keep failing.
What a hard bounce actually is
A hard bounce is a permanent delivery failure. The receiving server has looked at the recipient and decided it can never accept mail for that address. The SMTP reply comes back as a 5xx code, most commonly 550 (no such user) or 553 (mailbox unavailable).
Common causes:
- The mailbox does not exist. A typo (gmial.com), a made-up address, or an account that was deleted.
- The domain does not exist or has no mail server. No MX record, expired registration, or a dead host.
- You have been blocked at the address level. The recipient or their admin has explicitly rejected you.
Hard bounces are the expensive ones. Mailbox providers watch how often you send to addresses that bounce permanently, and a high rate is read as a signal that you bought a list or never clean it. That perception lands you in spam folders for the people who do exist.
What a soft bounce actually is
A soft bounce is a temporary delivery failure. The address is real and the server is reachable, but it cannot take the message right now. These return 4xx SMTP codes, like 421 (service unavailable) or 452 (insufficient storage).
Common causes:
- The mailbox is full. The user has not cleared space.
- The server is down or overloaded. A short outage or a rate limit.
- The message is too large. Attachments push it past the recipient's limit.
- Greylisting. The server deliberately defers first-time senders and expects a retry.
- A temporary reputation block. The receiver is throttling you for the moment.
How they differ at a glance
| Trait | Soft bounce | Hard bounce |
|---|---|---|
| SMTP code | 4xx (temporary) | 5xx (permanent) |
| Is the address valid? | Usually yes | No, or unreachable |
| Right action | Retry, then give up | Remove at once |
| Reputation hit | Low if managed | High, fast |
| Will it self-resolve? | Often | Never |
Exactly what to do about each
For hard bounces
- Suppress immediately. Any decent sending platform auto-removes hard bounces. If yours does not, do it by hand after every send.
- Never resend. Sending again to a confirmed dead address is the single fastest way to look like a spammer.
- Find the source. A cluster of hard bounces from one signup form usually means a missing validation step at the point of capture.
For soft bounces
- Let your platform retry. Most retry on a schedule for 24 to 72 hours before giving up.
- Set a strike limit. If an address soft bounces on three or four consecutive campaigns, treat it as effectively dead and suppress it.
- Read the reason. A wave of soft bounces across many recipients is rarely about them. It usually means your sending reputation or authentication is the problem.
The smarter move: stop the bounce before it happens
Every hard bounce is a failure you could have caught earlier. Cleaning a list after the damage is done means the bounce already counted against you. Verifying addresses before you send moves the check upstream, so dead addresses never reach the mailbox provider in the first place.
A verifier checks syntax, confirms the domain has a live mail server, and pings the mailbox to see whether it accepts mail, all without sending a real email. That is how you keep your hard bounce rate near zero. You can run a list through the free email verifier or wire it into your signup form, and see pricing for volume. For the wider picture, the email list hygiene guide and our notes on how to reduce email bounce rate go deeper.
FAQ
How many bounces are too many?
Keep your total bounce rate under 2 percent per campaign, and hard bounces well under 1 percent. Above that, mailbox providers start treating you with suspicion and deliverability drops for everyone on the list.
Can a soft bounce become a hard bounce?
Yes. If an address soft bounces repeatedly across several sends, most platforms reclassify it as permanently failed and suppress it. A persistent temporary failure is, in practice, a dead address.
Do bounces hurt my reputation even if the address is real?
Soft bounces barely register when handled correctly. Hard bounces hurt regardless of intent, because the metric providers track is how often you send to addresses that do not exist, not whether you meant to. That is why verifying before you send beats cleaning up afterward.