By MailTester.Ninja · July 08, 2026 · 15 min read · Email Deliverability
Your campaign dashboard shows bounces, but not all bounces are equal. The difference between a hard bounce vs soft bounce is the difference between a permanent dead end that damages your sender reputation the instant it happens and a temporary hiccup that resolves on its own. Treating them the same way is one of the most common and most expensive mistakes in email, because the wrong response to each one quietly wrecks your deliverability.
The difference between a hard bounce and a soft bounce comes down to one word: permanence. A hard bounce is a permanent failure, usually an address that does not exist. A soft bounce is a temporary failure, like a full inbox or a server that is momentarily down. Hard bounces you remove immediately. Soft bounces you retry. Get that backwards and you either lose reachable contacts or keep hammering dead addresses that poison your domain.
This guide breaks down hard bounce vs soft bounce completely: the exact definitions, the SMTP codes behind each, the 2026 benchmarks that should trigger action, when a soft bounce becomes a hard bounce, and how to fix both. The most important takeaway is simple: hard bounces are almost entirely preventable, and preventing them is the single highest-leverage thing you can do for your deliverability.
Search intents covered: "hard bounce vs soft bounce", "difference between hard and soft bounce", "what is a hard bounce", "what is a soft bounce", "soft bounce vs hard bounce email", "email bounce types", "what causes email bounces", "how to fix email bounces", "hard bounce meaning", "acceptable bounce rate"
Quick answer: hard bounce vs soft bounce A hard bounce is a permanent delivery failure, caused by an invalid or non-existent email address or an inactive domain. It returns a 5XX SMTP code and must be removed from your list immediately, never retried. A soft bounce is a temporary delivery failure, caused by a full inbox, a server that is down, or a message that is too large. It returns a 4XX SMTP code and can be retried, which email platforms do automatically for 24 to 72 hours. Hard bounces damage your sender reputation far faster than soft bounces, and unlike soft bounces, they are almost entirely preventable with pre-send email verification.
What Is an Email Bounce?
An email bounce happens when a message is not accepted by the recipient's mail server and is returned to you undelivered. When this occurs, the receiving server sends back an automated notice called a Non-Delivery Report, along with a numerical SMTP code and a short explanation of why delivery failed.
Every bounce falls into one of two categories based on that code and reason: hard or soft. The distinction is not cosmetic. It tells you whether the failure is permanent or temporary, which determines the only thing that matters next, what you should do about it. Tracking the two separately, rather than as a single combined bounce rate, is what lets you see the real health of your list.
What Is a Hard Bounce?
A hard bounce is a permanent delivery failure. The receiving server is telling you, definitively, that this email will never be delivered to this address. Retrying will not help, because nothing about the situation is going to change. The address is a dead end.
What causes a hard bounce
The most common cause. A typo at signup, a made-up address, or a mailbox that was deleted. The server returns "user unknown."
The domain never existed, expired, or no longer accepts mail. There is no server to deliver to.
The recipient's server has blocklisted your domain or IP, or rejects your mail outright for failing authentication.
A once-valid address that has been deactivated. Common with B2B contacts who changed jobs, since B2B data decays 22 to 25% per year.
What to do with a hard bounce: Remove it from your list immediately and never send to it again. Re-sending to hard bounces tells mailbox providers you are not maintaining your list, which is one of the fastest ways to damage your sender reputation and land in spam. Most email platforms suppress hard bounces automatically, but you should also verify your list before sending so they never happen in the first place.
What Is a Soft Bounce?
A soft bounce is a temporary delivery failure. The receiving server is reachable and the address is plausible, but something is preventing delivery right now. The situation may resolve on its own, so the correct response is to retry, which email platforms do automatically before giving up.
What causes a soft bounce
The recipient's mailbox has hit its storage limit. Once they clear space, mail can get through. Common with inactive subscribers.
The receiving server is temporarily offline, being patched, or throttling inbound traffic during a volume spike.
The email exceeds the server's size limit. Gmail caps at 25MB, and limits vary elsewhere. Common with heavy image attachments.
The server flagged your content or applied greylisting, a deliberate short delay for unknown senders that resolves on retry.
What to do with a soft bounce: Let your email platform retry automatically, which it does for 24 to 72 hours. A one-off soft bounce is normal and low risk. The danger is a repeated soft bounce to the same address across several sends, which signals an underlying problem. If an address soft bounces three or more times over a couple of weeks, treat it as a hard bounce and suppress or re-verify it.
Hard Bounce vs Soft Bounce: Side by Side
The core differences at a glance
Here is the full comparison at a glance. The differences in cause, code, and response are what make treating them separately so important.
Hard Bounce
Main cause
Invalid or non-existent address
Response
Remove immediately
Reputation impact
High and immediate
Preventable?
Yes, with verification
Soft Bounce
SMTP code
4XX (e.g. 421, 450)
Main cause
Full inbox or server issue
Response
Retry automatically
Retry?
Yes, for 24 to 72 hours
Reputation impact
Low, unless repeated
Preventable?
Partly, mostly out of your control
In short: A hard bounce is a permanent failure from an invalid address that returns a 5XX code and must be removed immediately. A soft bounce is a temporary failure from a full inbox or server issue that returns a 4XX code and should be retried. Hard bounces hurt your reputation more and faster, but they are preventable. Soft bounces are mostly outside your control, but become dangerous when they repeat to the same address.
The SMTP Codes Behind Each Bounce
Every bounce carries an SMTP status code that tells you exactly why it failed. The mental model is simple: codes starting with 5 are permanent (hard bounces), and codes starting with 4 are temporary (soft bounces), as defined in the SMTP standard (RFC 5321). Reading these codes turns a vague bounce report into a precise diagnosis.
| Code | Type | Meaning |
|---|
| 550 | Hard | Mailbox unavailable or user unknown. The address does not exist. |
| 550 5.7.515 | Hard | Access denied, sending domain does not meet the required authentication level. |
| 551 / 553 | Hard | User not local or invalid address format. Permanent rejection. |
| 421 | Soft | Service not available. The server is overloaded or temporarily refusing connections. |
| 450 | Soft | Mailbox unavailable temporarily. The mailbox exists but cannot accept mail right now. |
| 452 | Soft | Insufficient storage or too many recipients. Often a full inbox or rate limit. |
The code tells you where the problem lies. A 550 means the recipient's address is bad and you should remove it. A 550 5.7.515, by contrast, means the recipient is fine but your own domain failed authentication, so the fix is your SPF, DKIM, and DMARC setup, not the address. Learning to read these codes, and the statuses in our verification statuses guide, saves you from removing good contacts or keeping bad ones.
When a Soft Bounce Becomes a Hard Bounce
Here is a nuance that trips up many senders: a soft bounce does not stay soft forever. Email platforms convert a repeatedly soft-bouncing address into a hard bounce once it fails too many times, because a mailbox that is always full or always unreachable is, for practical purposes, dead.
The exact threshold varies by platform. Some convert after a fixed number of consecutive failures, others after a set retry window. A widely used rule of thumb is that an address soft bouncing three or more times across a two-week period should be treated as a hard bounce, suppressed, or re-verified before the next send.
| Platform approach | Typical conversion rule |
|---|
| Retry window | Suppress after 24 to 72 hours of failed retries |
| Consecutive failures | Convert to hard bounce after 3 to 7 consecutive soft bounces |
| Activity-based | Some platforms allow more soft bounces for previously active contacts before suppressing |
| Three-strike rule | Manual best practice: same address soft bounces 3+ times in 14 days, treat as hard |
This is why monitoring matters. A single soft bounce is noise, but a pattern of soft bounces to the same addresses is a signal that part of your list has gone stale and is quietly dragging down your deliverability. Re-verifying those addresses before they harden into hard bounces keeps your list clean and your reputation intact.
Bounce Rate Benchmarks for 2026
Knowing the difference between bounce types is only useful if you know what rates are healthy. These are the thresholds that matter in 2026, and the numbers mailbox providers actually watch.
| Metric | Healthy | Warning | Critical |
|---|
| Total bounce rate | Under 1% | 1 to 2% | Above 2% |
| Hard bounce rate | Under 0.5% | 0.5 to 2% | Above 2% |
| Soft bounce rate | Under 2% | 2 to 3% | Above 3% |
| Spam complaint rate | Under 0.1% | 0.1 to 0.3% | Above 0.3% |
The thresholds are not arbitrary. Since the 2024 Gmail and Yahoo bulk sender requirements, senders of more than 5,000 messages a day are expected to keep bounce rates trending below these lines, and a spam complaint rate above 0.3% actively hurts you. According to Google's sender guidelines, persistent high bounce rates are grounds for delivery deferral and domain-level blocking.
The key reframe: If your bounce rate is above 2%, you do not have a deliverability problem, you have a data quality problem. Deliverability is just the symptom. The cause is bad data: stale lists, unverified imports, or purchased contacts. A 3% hard bounce rate hits providers harder than a 5% soft bounce rate, which is why hard bounces are the priority for prevention.
How to Prevent Hard Bounces
The five steps that keep hard bounces near zero
This is the part that changes everything, because unlike soft bounces, hard bounces are almost entirely preventable. Every hard bounce from an invalid address is one you could have caught before sending. The fix is verification, and it is the highest-leverage move in all of deliverability.
Catch hard bounces before they happen MailTester.Ninja verifies every address with real-time SMTP checks, confirming the mailbox exists before you send. Catch-all detection and spam-trap flagging remove the risky addresses too, keeping your hard bounce rate near zero, at a fraction of incumbent prices.
Verify your listRun your list through
email verification to remove invalid mailboxes, the direct cause of hard bounces, before they ever reach the send queue. This alone brings hard bounces near zero.
B2B data decays 22 to 25% per year. A list that was clean months ago is already partly dead. Re-verify before every major send to catch newly invalid addresses.
For cold outreach especially, exclude uncertain addresses. Our
catch-all guide explains how to handle domains that accept all mail.
Catch typos and fake addresses at the point of entry with real-time validation on your forms, before they ever enter your list.
Set up SPF, DKIM, and DMARC so you never trigger a 550 5.7.515 authentication hard bounce, where the address is fine but your domain fails the check.
Preventing hard bounces protects your sender reputation, keeps your overall bounce rate low, and pairs with regular email list cleaning to keep your list permanently healthy. Combined with a run through an email deliverability test, verification is what keeps your emails landing in the inbox instead of bouncing or going to spam.
The bottom line: Hard bounces are permanent failures from bad addresses that you must remove and can prevent. Soft bounces are temporary failures you retry, watching for repeats. Track them separately, read the SMTP codes, and verify your list before every send. Do that, and you keep your hard bounce rate near zero and your deliverability strong.
Bounce Glossary
The key terms behind email bounces, in plain language.
| Term | What it means |
|---|
| Hard bounce | A permanent delivery failure, usually from an invalid or non-existent address. Returns a 5XX code. Remove immediately. |
| Soft bounce | A temporary delivery failure from a full inbox or server issue. Returns a 4XX code. Retry, then suppress if repeated. |
| Bounce rate | The percentage of sent emails that fail to deliver. Calculated as bounces divided by emails sent, times 100. |
| SMTP code | The numerical status a mail server returns. 5XX means permanent (hard), 4XX means temporary (soft). |
| NDR | Non-Delivery Report. The automated bounce message returned to the sender explaining why delivery failed. |
| Greylisting | A deliberate temporary rejection of mail from unknown senders, causing a soft bounce that resolves on retry. |
| Suppression | Removing an address from future sends. Hard bounces are suppressed immediately; soft bounces after repeated failures. |
| Spam trap | An address used to catch senders with poor list hygiene. Hitting one badly damages your reputation. |
Frequently Asked Questions
What is the difference between a hard bounce and a soft bounce?
A hard bounce is a permanent delivery failure, caused by an invalid or non-existent email address or an inactive domain, and it returns a 5XX SMTP code. A soft bounce is a temporary delivery failure, caused by a full inbox, a server that is down, or a message that is too large, and it returns a 4XX SMTP code. The key difference is the response: hard bounces must be removed from your list immediately and never retried, while soft bounces should be retried, which email platforms do automatically for 24 to 72 hours before giving up.
Are hard bounces or soft bounces worse?
Hard bounces are worse for your sender reputation and damage it faster, because they signal to mailbox providers that you are sending to addresses you should not have. A single hard bounce carries more weight than a single soft bounce. In fact, a 3% hard bounce rate hits providers harder than a 5% soft bounce rate. That said, repeated soft bounces to the same addresses are also damaging over time, because they indicate a stale list that you are not cleaning. Both should be managed, but hard bounces are the priority for prevention.
Can a soft bounce become a hard bounce?
Yes. Email platforms convert a repeatedly soft-bouncing address into a hard bounce once it fails too many times, because a mailbox that is always full or unreachable is effectively dead. The exact threshold varies: some platforms convert after 3 to 7 consecutive failures, others after a retry window of 24 to 72 hours. A common manual best practice is the three-strike rule: if the same address soft bounces three or more times across a two-week period, treat it as a hard bounce and suppress or re-verify it before your next send.
What causes a hard bounce?
Hard bounces are caused by permanent delivery failures. The most common cause is an email address that does not exist, from a typo at signup, a fake address, or a deleted mailbox. Other causes include an invalid or expired domain that no longer accepts mail, a recipient server that has permanently blocked your domain or IP, and abandoned mailboxes from contacts who changed jobs. Since B2B data decays 22 to 25% per year, natural list aging is a major hidden source of hard bounces, which is why regular verification matters.
What causes a soft bounce?
Soft bounces are caused by temporary delivery failures where the server is reachable but cannot deliver right now. The most common causes are a full recipient inbox that has hit its storage limit, a receiving server that is temporarily down or overloaded, a message that exceeds the server's size limit (Gmail caps at 25MB), and temporary content or policy filters like greylisting. Because these issues usually resolve on their own, email platforms automatically retry soft bounces for 24 to 72 hours before treating the address as undeliverable.
What is a good bounce rate?
A total bounce rate below 1% is excellent, 1 to 2% is acceptable, 2 to 5% is concerning, and above 5% is dangerous. Broken down by type, your hard bounce rate should stay below 0.5%, ideally near zero, while a soft bounce rate under 2% is generally fine. Since the 2024 Gmail and Yahoo requirements, bulk senders are expected to keep bounce rates trending below these lines, and persistent rates above 2% can lead to delivery deferral and domain blocking. Tracking hard and soft bounces separately, rather than as one number, gives you the clearest picture.
How do I stop emails from bouncing?
The single most effective step is to verify your email list before sending, which removes the invalid addresses that cause hard bounces. Beyond that, re-verify lists older than 90 days since data decays over time, validate addresses at signup to catch typos, segment out catch-all and risky addresses for cold outreach, and set up SPF, DKIM, and DMARC authentication to avoid authentication-based hard bounces. For soft bounces, let your platform retry automatically and suppress addresses that repeatedly fail. Verification is the highest-leverage action because it prevents the most damaging bounce type entirely.
Do soft bounces hurt my sender reputation?
A single soft bounce has minimal impact on your sender reputation, because mailbox providers expect occasional temporary failures. The danger is a consistent pattern of soft bounces to the same addresses across multiple sends, which signals that you are not cleaning your list and inflates your total bounce rate. Over time, this drags down your reputation and inbox placement just as hard bounces do. The rule is simple: occasional soft bounces are normal, but repeated soft bounces to the same address should be treated as a stale record and suppressed or re-verified.
What does SMTP code 550 mean?
SMTP code 550 is a permanent failure indicating the mailbox is unavailable or the user is unknown, meaning the address does not exist. It is a hard bounce, so the address should be removed from your list immediately. A related code, 550 5.7.515, means something different: access was denied because your sending domain does not meet the required authentication level. In that case the recipient's address is fine, but your domain failed SPF, DKIM, or DMARC, so the fix is your authentication setup rather than the address. In general, any 5XX code is a permanent hard bounce, while any 4XX code is a temporary soft bounce.
Can verification prevent all bounces?
Verification prevents nearly all hard bounces, because it confirms an address exists before you send, removing the invalid mailboxes that cause them. It cannot prevent all soft bounces, since those come from temporary issues like a full inbox or a server being down, which are outside your control and not visible at verification time. The realistic goal is a hard bounce rate near zero from verification and clean list hygiene, plus a low soft bounce rate managed through automatic retries and suppression of repeat offenders. Together, that keeps your total bounce rate comfortably under 1%.
About the author
COO at MailTester.Ninja
Danila has spent the last few years deep in email deliverability, helping SaaS companies and growth teams fix the infrastructure problems that silently kill their outbound results. As COO of MailTester.Ninja, he oversees product and operations with a single obsession: making email verification fast, accurate, and genuinely useful for the people who need it most.
Stop hard bounces before they start
Hard bounces come from invalid addresses, and invalid addresses are exactly what MailTester.Ninja catches. Verify every address with real-time SMTP accuracy, flagging invalid, disposable, and catch-all addresses plus spam traps. Keep your hard bounce rate near zero and your sender reputation protected.
Verify your list for freeReal-time SMTP verification · Catch-all detection · Spam trap flagging · Zero data storage
