Article

Hard Bounce vs Soft Bounce Codes: How to Classify and Act on Them

By Unlimited Verifier Team ·

Flowchart showing how an SMTP reply code splits into hard bounce 5xx and soft bounce 4xx paths for SMTP bounce code classification.

Summary

A hard bounce is a permanent 5xx SMTP failure that means the address will never accept mail, while a soft bounce is a temporary 4xx failure that may succeed on retry. The first digit of the reply code gives the verdict, and the enhanced status code explains the cause. Classify by code, suppress hard failures on bad addresses, and quarantine soft bounces until they fail repeatedly.

A hard bounce is a permanent delivery failure, usually signalled by a 5xx SMTP reply such as 550 5.1.1, that tells the sender an address will never accept mail. A soft bounce is a temporary failure, usually a 4xx reply such as 421 4.7.0 or 452 4.2.2, where the same message may succeed on a later attempt.

The first digit gets you most of the way, but not all of it. Some 5xx codes are policy blocks on perfectly good addresses, and some 4xx codes never clear. This guide shows how to classify bounces correctly, when to suppress, and how to confirm the result before you act. For the wider context, start with our pillar on email bounce codes.

Quick answer

What is the difference between a hard bounce and a soft bounce?

A hard bounce is the receiving server's final answer, and a soft bounce is its "not right now." The distinction describes one delivery attempt, not a permanent label on the address. The same mailbox can soft-bounce today and hard-bounce next month.

RFC 5321, the SMTP standard, sorts replies by their first digit: 4yz is a transient negative completion (try again), and 5yz is a permanent negative completion (don't). Your sending platform records the reply it received and labels the bounce hard or soft from that.

Factor Hard bounce Soft bounce
SMTP reply class 5xx (permanent) 4xx (transient)
Server's intent "Don't retry" "Try again later"
Typical examples 550 5.1.1, 554 5.7.1 421 4.7.0, 452 4.2.2
Typical cause Address doesn't exist, domain invalid, or blocked by policy Full mailbox, throttling, temporary server problem
Default action Suppress or investigate Quarantine and retry
Risk if ignored Damages sender reputation Becomes hard over time, or wastes sends

Bottom line: Hard means the server has ruled the attempt out permanently; soft means it has deferred the decision. Give them different workflows.

How do SMTP codes tell hard and soft bounces apart?

The first digit of the reply code gives the verdict: 4 means retry, 5 means don't. Most receiving servers also return an enhanced status code in the form X.Y.Z. The X repeats the class (2 success, 4 persistent transient failure, 5 permanent failure), while Y and Z say what went wrong. RFC 3463 defines the enhanced codes.

Read 550 5.1.1 from left to right:

The Y digit tells you where the problem sits:

Y digit Subject Example codes What it usually signals
0 Other or undefined 5.0.0, 4.0.0 Generic; read the text
1 Addressing 5.1.1, 5.1.2 Recipient address or domain problem
2 Mailbox 5.2.1, 5.2.2, 4.2.2 Mailbox disabled or full
3 Mail system 4.3.0, 5.3.x Server-side storage or system fault
4 Network and routing 4.4.1 Host unreachable or no answer
5 Mail delivery protocol 5.5.x Protocol or command errors
6 Media or content 5.6.x Message format or conversion problems
7 Security and policy 5.7.1, 5.7.x Blocked by policy, reputation or authentication

The catch: providers don't use codes consistently. RFC 3463 lists "mailbox full" under both 5.2.2 and 4.2.2. Which one a receiver returns depends on that receiver's policy, so one provider may reject a full mailbox permanently while another defers it. Some servers also return a three-digit reply with no enhanced code, so your classifier should fall back to the first digit when the enhanced code is missing. For a fuller breakdown, see 4xx versus 5xx SMTP errors.

Bottom line: The class digit gives the verdict, the subject digit gives the category, and the text explains the rest. Always keep the raw diagnostic text, not just a label.

Which bounce codes are hard bounces?

The codes that mean the address itself is invalid are 5.1.1, 5.1.2 and 5.2.1. Codes in the 5.7.x family are also hard-class, but they describe the sender or the policy at that moment, so they need a different response.

Code Meaning in brief Hard or policy? Our default action
550 5.1.1 Bad destination mailbox; the user doesn't exist Hard, address invalid Suppress immediately; see user-unknown errors
550 5.1.2 Bad destination system address (host or domain) Hard, domain invalid Suppress; check the domain for typos. Background in bad destination host codes
5.2.1 Mailbox disabled, not accepting mail Hard, address dormant Suppress
5.2.2 Mailbox full (permanent class) Hard class, often temporary in practice Quarantine; suppress after repeats
554 5.7.1 or 550 5.7.1 Refused by policy, reputation or content Hard class, sender-side cause Don't mark invalid; investigate. Read 554 5.7.1 policy blocks

The 5.7.x family needs the most care. Its reply text usually points at your message, your sending IP or your authentication, not the recipient's mailbox. If you suppress these contacts as invalid, you may discard engaged subscribers, and the underlying problem (reputation, content or authentication) will still hurt the rest of your sends.

Bottom line: Only the 5.1.x and 5.2.1 family reliably means "this address should not get mail." Read the 5.7.x text before you decide.

Which bounce codes are soft bounces?

Soft bounces are deferrals. The receiving system is asking you to try again later, and the sending server handles most of the retries. These are the codes you will see most often.

Code Meaning in brief Typical cause Our default action
421 4.7.0 Temporary deferral, often for rate or reputation Your sending volume or IP reputation at that provider Slow down and retry; see the 421 4.7.0 guide
450 4.2.0 Mailbox status undefined; often a temporary lock Mailbox locked, or server busy Retry later; see 450 deferrals
452 4.2.2 Mailbox full Recipient over storage quota Quarantine; count repeats
451 4.3.0 Local processing error Receiving server fault Retry; no action on the address
4.4.1 No answer from host Connection timed out Retry; check if it persists

Soft bounces that never clear. A mailbox that stays full for several weeks has effectively gone dormant. A throttle that keeps recurring usually points to your own sending pattern. Track each address's soft-bounce history so that repeated failures move the contact into a hard state in your records. For the most frequent causes, see our common soft bounce reasons list.

Bottom line: Most soft bounces are either a recipient's storage problem or your sending rate. Only a recipient's problem should count against that recipient.

Why are some hard bounces not invalid addresses?

A hard bounce records a refusal, and refusals have many causes. Only some of them mean the address is dead. The rest are about the sender, the content or the provider's policy at that moment.

Three patterns cause most misclassification:

  1. Reputation blocks. A provider rejects mail from an IP or domain it no longer trusts. Every address in that send can get a 5.7.x code, including valid ones.
  2. Authentication or content failures. Missing or misaligned SPF, DKIM or DMARC, or content the filter dislikes, can produce policy codes that look like address problems in your log.
  3. Recipient-side policy. Some corporate mail systems reject senders outright. The address exists, but that recipient won't accept your mail.

The error runs both ways. Suppressing a 5.7.1 contact may remove a valuable customer. Retrying a 5.1.1 contact keeps you sending to a dead address and worsens your reputation. Split these into separate suppression reasons so a later audit can tell "invalid address" from "blocked sender."

Bottom line: Record the reason, not just the bounce type. A suppression list with "invalid" and "policy" entries is far more useful than one with a single "bounced" flag.

How many soft bounces before you suppress an address?

Suppress after three soft bounces spread across at least seven days. Platforms don't publish a common standard, and some suppress on the first hard bounce while others keep retrying soft-bounced contacts for weeks. We recommend a rule you can explain in an audit:

The reasoning behind the timing:

Bottom line: Quarantine on the first soft bounce and suppress after three failures spread over at least a week.

Is a bounce code the same as a bad email address?

No. A bounce code is evidence from one send, while verification is a check you run before sending. The two overlap, but they see different things.

Signal When you get it What it reliably tells you Blind spot
ESP bounce code After sending The receiving server's verdict on that attempt Silent on catch-all domains; mixes policy with validity
Pre-send verification Before sending Syntax, domain, MX, SMTP mailbox response, catch-all, disposable and role flags Can't prove consent; a provider's decision can change later
Engagement data Over weeks Whether the person is interested Some privacy features inflate opens; silence isn't proof of invalidity

The catch-all problem. A catch-all domain accepts mail for any address at the SMTP stage, so a non-existent mailbox produces no bounce at all. Your log shows "delivered," and the address quietly does nothing. Bounce codes alone therefore understate the invalid share of a list. Catch-all detection fills that gap, and such addresses belong in Risky, not Valid. Our catch-all email verification page explains how these results are handled.

If you're comparing options for this step, our guide to the best email verification tools lays out what to look for.

Bottom line: Bounce codes tell you what happened, verification tells you what is likely to happen, and engagement tells you whether anyone cares. Use all three.

How do you classify bounces in a real send log?

Use this seven-step framework. It turns a raw log into four decisions: suppress, hold for policy review, quarantine, or verify.

  1. Export the raw bounce data. Include the reply text or diagnostic field, not only the category. Summaries hide the codes you need. If you're unsure which reply code a message used, check the MAILER-DAEMON bounce messages explainer for where it appears.
  2. Split by the first digit. Separate 4xx (soft) from 5xx (hard). Count each, and calculate both rates against total sends.
  3. Sub-classify by enhanced code. Group 5.1.x and 5.2.1 as address problems, 5.7.x as policy, and 5.2.2 or 4.2.2 as mailbox full.
  4. Assign each row one bucket. Suppress (address invalid), Policy hold (5.7.x), Soft quarantine (4xx and 5.2.2), or Unknown (no code or unclear text).
  5. Apply your suppression rules. Suppress the first bucket permanently. Apply the three-strike rule to soft quarantine.
  6. Verify the ambiguous buckets. Run Soft quarantine and Unknown contacts through a verifier to see which are Valid, Risky or Invalid.
  7. Track the trend. Measure the hard-bounce rate per send, and track how many soft-bounce contacts convert to hard after three failures. Rising conversion means your list is aging.

Bottom line: Classify by code, decide by bucket, then confirm with verification. The sequence matters, because verification is most useful on the contacts your codes can't settle.

How do you sort a bounce log and verify the results?

Export the bounce log, sort each row into a bucket, verify the uncertain buckets, and re-import only the addresses that come back Valid. Because Unlimited Verifier has no native ESP, CRM or Zapier integration, the workflow is export, verify, re-import, or calling the API from your own scripts.

  1. Export your bounce report as CSV. Include the email address, the bounce type, the reply code or diagnostic text, and the send date. Export the full send list separately so you can reconcile totals.
  2. Build a working sheet. Add a column called bucket and mark each row Suppress, Policy hold, Soft quarantine or Unknown, using the rules above. If the reply code sits in column C as text, =COUNTIF(C:C,"5.1.1*") counts those rows.
  3. Create the verification file. Copy the Soft quarantine and Unknown rows into a new CSV. Add Policy hold rows too if you want to know whether those addresses are valid.
  4. Check the file against your plan limits. On the Free plan, each list holds up to 150 emails and you can run 25 lists a month. On Pro, each list holds up to 25,000 emails.
  5. Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically.
  6. Read the three buckets. Valid addresses are safe to return to sending. Invalid addresses go to suppression. Risky addresses, which include catch-all domains, disposable addresses and role accounts such as info@, stay out of the active list until you decide on them.
  7. Export the results the same day. Export as CSV, Excel or JSON. Results are kept for 24 hours on the Free plan and 30 days on Pro, so download them promptly.
  8. Re-import in three segments. Valid returns to the sending list, Invalid goes to your ESP's suppression list, and Risky stays in a held segment. Keep your own copy of the suppression file, because suppression history doesn't always migrate between platforms.
  9. Automate when volume grows. For single checks at signup, or bulk batches of up to 10,000 emails per request, use the email verification API (see email verification API and automation for workflow patterns). API access is included on Pro, with 100,000 emails a month. For a quick spot check on one address, use the free email checker.

To catch these addresses before they bounce, see our guide to real-time email validation.

Bottom line: Export the codes, sort them, verify the uncertain buckets, and re-import only what came back Valid.

How do you act on a 40,000-recipient bounce log?

Start with the rate, then split it by bucket, then decide what to do with each group. The figures below are hypothetical, but the arithmetic and plan limits are real.

Imagine a campaign to 40,000 recipients that produced 1,200 bounces.

Overall rate: 1,200 ÷ 40,000 = 3.0%, above the 2% ceiling we recommend.

Breakdown from the raw log:

Bucket Codes Count Share of sends
Hard, address invalid 5.1.1 (610), 5.1.2 (45), 5.2.1 (30) 685 1.71%
Hard, policy 5.7.1 95 0.24%
Soft, mailbox full 4.2.2 260 0.65%
Soft, throttling 4.7.0 90 0.23%
Soft, other Various 4.x.x 70 0.18%
Total 1,200 3.00%

Check the sums: 685 + 95 + 260 + 90 + 70 = 1,200. The hard total is 780 ÷ 40,000 = 1.95%, and the soft total is 420 ÷ 40,000 = 1.05%. Shares are rounded to two decimals.

Decisions:

Verifying the 420 soft-bounce contacts: On the Free plan, each list holds up to 150 emails, so 420 contacts need three lists (150 + 150 + 120), using 3 of your 25 monthly lists. On Pro, the same 420 contacts fit in one list. Unlimited standard verification is included on every plan, so there is no per-email charge either way. Deep verifications are a separate allowance (750 a month on Free, 25,000 on Pro), so spend them on the riskiest contacts first. For the cost side of this decision, see email verification pricing.

Hypothetical results:

Check: 330 + 60 + 30 = 420.

Resulting list:

What this shows: Verifying before the send would likely have caught many of the 610 user-unknown addresses. The 330 Valid soft-bounce contacts still aren't fully trusted, because a full mailbox can bounce again. Re-test them after two weeks, and aim for a hard-bounce rate under 0.5% on the next campaign.

Bottom line: From this 40,000-recipient campaign, 685 contacts are removed permanently, 155 are held, and the soft-bounce group is re-tested rather than trusted on a single check.

What bounce rate counts as a problem?

Sources disagree, and most platforms don't publish exact figures. Here is what the public documentation says, and the number we recommend.

Source Metric Figure Notes
Amazon SES documentation Bounce rate 5% triggers review; 10% can lead to pause Describes its own sending service
Google's sender guidelines Spam rate Keep below 0.3% A complaint metric, not a bounce metric
Yahoo sender requirements Spam rate Similar expectations to Google Also a complaint metric
Our recommendation Hard-bounce rate Under 0.5% per send Practitioner guidance
Our recommendation Total bounce rate Goal under 1%, ceiling 2% Leaves room before automated triggers

Three points matter here. Bounce rate is usually measured against attempted sends, and definitions differ between platforms. Spam complaints and bounces are separate metrics, so don't mistake Google's 0.3% spam-rate expectation for a bounce threshold. And the platform figures mark where automated action can start, so planning to a lower internal target keeps you clear of them.

Bottom line: Plan for hard bounces under 0.5% and total bounces under 2%, and treat the 5% figure as an outer boundary, not a target. For ESP-specific thresholds, see what bounce rate gets your ESP account suspended.

What should you look for in a verifier for bounce triage?

Choose a verifier that returns categories you can act on, flags catch-all domains, keeps results long enough to export, and offers an API for ongoing checks. The table below lists the criteria that matter most for bounce triage and the question to ask each vendor. For a full comparison framework, see how to choose an email verifier.

Criterion Why it matters for bounces Question to ask
Result categories Suppress, hold and re-test need different buckets Are results split into Valid, Risky and Invalid, or a single pass/fail?
Catch-all handling Catch-all domains hide invalid mailboxes from bounce logs Is catch-all detected and labelled, rather than marked Valid?
Disposable and role flags Role addresses like info@ rarely belong in a sending list Are these flagged separately?
Result retention Results you can't export are results you can't audit How long are results stored, and on which plan?
Batch and API limits Ongoing hygiene needs bulk and single-address checks What is the largest batch per request, and is API access included?

Unlimited Verifier sorts results into Valid, Risky and Invalid, flags catch-all, disposable and role-based addresses, and exports to CSV, Excel or JSON. Its Free plan keeps results for 24 hours, and Pro keeps them for 30 days. Those retention windows matter for the audit trail, so export on the same day you verify.

Bottom line: A verifier is only useful for bounce triage if its results separate the buckets you need to act on. Check the categories and retention before you commit.

What are the most common bounce-handling mistakes?

Most bounce mistakes come from treating a refusal as a verdict on the address. These are the errors we see most often.

Bottom line: Read the code, record the reason, and confirm before you delete.

How we compared (and limitations)

This guide is based on public documentation: the SMTP and enhanced status-code RFCs (RFC 5321 and RFC 3463), Google and Yahoo sender guidelines, Amazon SES's published thresholds, and Postfix's documented queue behaviour. We have not tested any ESP's bounce handling directly, and providers can change codes and thresholds without notice.

Three limitations matter in practice:

For the consent side of list hygiene, see email verification compliance and hygiene and our email list maintenance best practices. If your bounces come from a list you're about to mail for the first time, sign up and verify it before the next campaign.

Bottom line: Use the codes to decide what happened, and verification to confirm what to do about it.

Bounce triage steps

  1. Read the 3-digit reply. 4xx = soft, 5xx = hard.
  2. Read the enhanced code (X.Y.Z). Note the Y and Z digits for the cause.
  3. If 5.1.1, 5.1.2 or 5.2.1: suppress immediately.
  4. If 5.7.1 or other policy/reputation codes: investigate sender reputation and authentication before suppressing.
  5. If 4xx: quarantine and retry on a later send.
  6. After 3 soft failures on separate sends across at least 7 days: suppress.
  7. Verify the address before re-mailing held or policy-blocked contacts.

Frequently asked questions

What is the difference between a hard bounce and a soft bounce?

A hard bounce is a permanent delivery failure, usually a 5xx SMTP reply, meaning the address will never accept mail. A soft bounce is a temporary failure, usually a 4xx reply, where the message may succeed on a later attempt. The label describes one delivery attempt, not the address permanently.

Is a 550 bounce always a hard bounce?

Usually yes. A 550 reply is a permanent negative completion, so it is treated as hard. However, 550 can also signal a policy or reputation block on a valid address, so check the enhanced code, such as 5.1.1 for an unknown mailbox or 5.7.1 for a policy rejection.

What does a 421 4.7.0 error mean?

A 421 4.7.0 reply is a temporary rejection, often from throttling or a server-side rate limit. It is a soft bounce, so the sender should retry later. If it keeps recurring, the sending IP or domain may be rate limited or flagged, and sending volume or authentication should be reviewed.

How many soft bounces before I suppress an address?

A common approach is to suppress after three soft failures on separate sends spread over at least seven days. Immediate retries rarely help because many temporary conditions, such as a full mailbox, clear slowly. Adjust the threshold to your own volume and risk tolerance.

Should I remove addresses after one hard bounce?

For clear invalid-address codes such as 5.1.1, 5.1.2 and 5.2.1, suppress immediately, since retrying does not help. For policy or reputation codes like 5.7.1, investigate first, because the address may be real and engaged.

What is an enhanced status code?

An enhanced status code takes the form X.Y.Z, defined in RFC 3463. The first digit repeats the class: 2 for success, 4 for persistent transient failure, and 5 for permanent failure. The second and third digits give the subject and detail, which helps explain the cause of a bounce.

Why does a soft bounce become a hard bounce over time?

Some temporary conditions never clear, such as a mailbox that stays full, a domain that stops accepting mail, or a server that retires an account. When a soft bounce repeats without resolution, the receiving server may eventually return a permanent 5xx reply, which then counts as hard.

Can an email verifier tell me whether a bounce is hard or soft?

A verifier cannot read the bounce from a real send, but it can check an address before you send. It helps separate likely-invalid addresses from policy-blocked or catch-all uncertain ones, so you can keep valid addresses, suppress invalid ones and hold risky ones for review.

Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification

Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.

Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.

Free Pro
Price $0 $29/month ($25/month billed annually)
Lists 25 a month, up to 150 emails each Unlimited, up to 25,000 emails each
Deep verifications 750 a month 25,000 a month
API access No Yes (100,000 emails a month)
Result retention 24 hours 30 days

Why teams choose Unlimited Verifier

Unlimited Verifier states 99.5% accuracy for deep verification.

Create a free account and verify your next list before you hit send.

Want to test a single address first? Try the free email checker.