Article
Types of Email Bounces With Examples: 9 Codes Explained
By Unlimited Verifier Team ·

Summary
Email bounces are either hard (permanent 5xx failures, such as a nonexistent mailbox at 550 5.1.1) or soft (temporary 4xx failures, such as a full inbox at 452 4.2.2). Classify each bounce by its enhanced status code rather than its wording, then apply the matching action: suppress hard bounces, retry soft ones and fix authentication or reputation for blocks.Email bounces come in two main types: hard bounces, which are permanent 5xx failures such as a nonexistent mailbox (550 5.1.1), and soft bounces, which are temporary 4xx failures such as a full inbox (452 4.2.2). Classify every bounce by its enhanced status code, not by its wording.
This guide covers the nine bounce patterns you'll meet most often. For each one you get the code, example wording, the usual cause, the right action and where a pre-send check can help. It's written for marketers, list owners, agencies and SaaS teams working on email verification compliance and hygiene. For the wider code reference, start with our email bounce codes guide.
Quick answer
- Hard bounce: permanent. Suppress the address after one occurrence. Common codes: 5.1.1, 5.1.2, 5.1.3.
- Soft bounce: temporary. Retry it, and treat the address as hard after three consecutive soft bounces (our recommendation; platforms differ).
- Block (often 5.7.x): the address may be valid. Fix authentication, reputation or content instead of deleting contacts.
- Target: keep hard bounces under 1% per send. Many ESPs and deliverability guides flag problems around 2%, so 1% leaves headroom.
- Pre-send check: Unlimited Verifier checks syntax, domain/MX and the SMTP mailbox, and detects catch-all domains. That catches many hard-bounce causes before you send, but not all of them.
Quick picks
- Most common hard bounce: nonexistent mailbox, 550 5.1.1.
- Most often misdiagnosed: policy blocks, 550 5.7.1 and 550 5.7.26. The address is usually fine.
- Most common soft bounce: mailbox full, 452 4.2.2.
- Hardest to predict: catch-all domains, which accept mail at send time and can hide failures.
| Bounce type | Typical code | Example wording (illustrative) | Hard or soft | Right action |
|---|---|---|---|---|
| Nonexistent mailbox | 550 5.1.1 | "The email account that you tried to reach does not exist" | Hard | Suppress |
| Domain or host unreachable | 550 5.1.2 | "Bad destination system address" | Hard (check DNS first) | Verify domain, then suppress |
| Invalid syntax | 550 5.1.3 | "Bad destination mailbox address syntax" | Hard | Fix or suppress |
| Policy or authentication block | 550 5.7.1, 550 5.7.26 | "Message rejected due to policy" / DMARC failure | Block | Fix sending; don't suppress |
| Mailbox full | 452 4.2.2 (soft); 552 5.2.2 (hard) | "Over quota" | Depends on code | Retry, then suppress on repeat |
| Throttling or deferral | 421 4.7.0, 450 4.2.1 | "Try again later" / rate limit | Soft | Retry, slow the send |
| Message too large | 552 5.3.4 | "Message size exceeds fixed maximum" | Message-level | Reduce message size |
| Catch-all acceptance | None | Message accepted, no bounce | Undetermined | Verify, segment by engagement |
| Undetermined | None or partial | Auto-reply, DSN with no usable code | Varies | Read the raw message |
Provider wording varies. The enhanced code is the stable part, so classify on it.
How we compared (and limitations)
Each bounce type was assessed on four criteria, based on public documentation:
- Code meaning: the enhanced status code's definition in RFC 3463 and the reply-code classes in RFC 5321.
- Observable wording: example text drawn from published provider documentation and commonly seen bounce messages. Examples are illustrative.
- Action: what should change in your list or your sending.
- Pre-send detectability: whether a verification check could predict the bounce before a send.
Limitations. Providers don't publish their full bounce-classification rules, and the same code can mean slightly different things on different servers. We did not run sending tests of our own. A verifier's "Invalid" result predicts a hard bounce; it doesn't guarantee one, and some mail servers don't confirm mailbox existence at all. For a wider tool comparison, see our best email verification tools roundup.
Bottom line: the enhanced code tells you more than the wording, and no verifier predicts every bounce.
How do you tell hard and soft bounces apart?
The first digit of the reply code is the fastest signal. A 4xx reply is temporary, so retry. A 5xx reply is permanent, so stop sending to that address. The enhanced code (X.Y.Z, defined in RFC 3463) adds detail. The first digit is the class: 2 means success, 4 means persistent transient failure, 5 means permanent failure. The second digit is the subject: 1 addressing, 2 mailbox, 3 mail system, 4 network and routing, 5 mail delivery protocol, 6 message content, 7 security or policy.
The practitioner rule: some servers return a permanent 5xx code for a full mailbox, and a 550 can mean a policy block rather than a missing address. The enhanced code (5.2.2 vs 5.7.1, for example) is what separates them. ESPs also label bounces differently, so check how your platform defines each category before comparing rates across tools. For a side-by-side reference, see hard bounce vs soft bounce codes.
Bottom line: read the enhanced code first; the wording and the first digit can mislead you.
What are the hard bounce types?
Hard bounces should change your list. They're mostly caused by stale data or weak signup forms.
1. Nonexistent mailbox (550 5.1.1)
What it means: the receiving server accepts that the domain exists but has no user at that address. It's the most common hard bounce on aging lists, because people change jobs, close accounts or mistype their address at signup.
Example wording (illustrative): "550-5.1.1 The email account that you tried to reach does not exist."
Common causes: a former employee's work address, an account the owner closed, or a typo in a domain that resolves to a real mail server. For the server-side detail, see 550 5.1.1 user unknown meaning.
Classification and action: hard. Suppress after one occurrence, and add the address to your ESP's suppression list, not just the contact record.
Where verification helps: an SMTP mailbox check flags many of these before you send, though not all, because some servers won't confirm mailbox existence.
Tip: if suppressed addresses come back after a CRM sync, the suppression list isn't wired into that import. Fix the sync before the next send.
Bottom line: one hard bounce is enough; suppress at the list level so the address can't return.
2. Domain or host unreachable (550 5.1.2)
What it means: the sending server can't find a usable receiving host for the domain. The usual causes are a lapsed domain, a misspelling or broken MX records. Because DNS faults can be temporary, check the domain before suppressing anyone.
Example wording (illustrative): "550 5.1.2 Bad destination system address." See 550 5.1.2 bad destination host meaning for more.
Pattern to watch: many addresses at one domain bouncing 5.1.2 in the same send points to the domain, not to individuals. One lapsed company domain can produce hundreds of bounces at once.
Classification and action: hard, but confirm the domain's MX records before suppressing the segment. Suppress only once the domain is confirmed as dead.
Where verification helps: Unlimited Verifier checks domain and MX records, so a domain with no working mail routing can be flagged before you send.
Tip: group bounces by domain in your export. Domain clusters are much faster to spot that way than by reading rows one at a time.
Bottom line: the domain is the diagnosis; confirm it before you delete a whole segment.
3. Invalid address syntax (550 5.1.3)
What it means: the address isn't formatted as a valid mailbox, for example a space in "jane doe@company.com" or a doubled @ in "mark@@company.com".
Example wording (illustrative): "550 5.1.3 Bad destination mailbox address syntax."
Classification and action: hard. Correct the address only if the intended one is obvious and you can confirm it with the subscriber. Otherwise suppress it.
Where verification helps: syntax checks catch these instantly. They usually enter through unvalidated forms or bulk imports.
Practitioner insight: a steady trickle of syntax failures is a form problem. A sudden batch from one import is more often a CSV problem, such as a delimiter that shifted the email column. Fix the input with real-time email validation so malformed strings never reach the database. SaaS signup forms are the usual entry point; our guide to email verification for ecommerce and SaaS covers that setup.
Bottom line: syntax failures are cheap to prevent, so fix them at the form, not in the send log.
Are policy blocks hard bounces?
No. Policy blocks look like hard bounces in a report, but they reflect your sending, not the recipient. They're the most damaging misreading in bounce analysis.
4. Policy and authentication blocks (550 5.7.1, 550 5.7.26)
What it means: the recipient's server recognized the address but refused the message because of authentication, sending reputation or content. For example, Gmail uses 5.7.26 when a message fails authentication and the sender's DMARC policy requires enforcement. A 5.7.1 code is usually a reputation, content or policy signal. A related 554 variant is covered in our 554 5.7.1 guide.
Example wording (illustrative): "550-5.7.26 Unauthenticated email is not accepted due to domain's DMARC policy." Wording varies by provider.
Classification and action: block. The address may be perfectly valid, so suppressing it removes a real reader and leaves the cause in place. Confirm that SPF, DKIM and DMARC pass and align for your sending domain, then check your reputation in Google Postmaster Tools. Google's sender guidelines advise keeping the user-reported spam rate below 0.1% and avoiding a rate of 0.3% or higher.
Where verification helps: it doesn't. A verifier evaluates the address, not your authentication or content, so don't expect it to predict these.
Tip: if blocks start on one provider the same day you change a sending domain or DNS record, check authentication before anything else.
Bottom line: a block means fix the sending; a hard bounce means fix the list.
What are the soft bounce types?
Soft bounces should be retried, but with a cap. The goal is to separate temporary problems from addresses that will never accept mail.
5. Mailbox full (452 4.2.2, or 552 5.2.2)
What it means: the recipient's mailbox has no room. A 4xx reply means the server may accept the message later. Some servers return a permanent 552 5.2.2 instead, which should be classed as hard.
Example wording (illustrative): "452 4.2.2 The email account that you tried to reach is over quota."
Classification and action: soft. Retry. Sources disagree on how many retries are enough. Some platforms give up after one soft bounce, others keep retrying for days. We recommend suppressing after three consecutive soft bounces across separate sends.
Practitioner insight: repeated over-quota bounces often come from accounts nobody reads anymore. If an address keeps hitting quota and hasn't opened in months, treat it as dead rather than retrying indefinitely. The sunset rule belongs in your email list maintenance best practices.
Where verification helps: it can't see mailbox quota, so a full mailbox can still pass verification.
Tip: track consecutive soft bounces per address as a tag in your ESP. Counting them is easier than reconstructing the history from logs.
Bottom line: retry, count, and convert to suppression at the third consecutive soft bounce.
6. Deferral and throttling (421 4.7.0, 450 4.2.1)
What it means: the receiving server asks you to slow down. Typical text is "try again later" or a rate-limit notice. It usually happens when volume to that provider exceeds its limits or your reputation there is under review. See 421 4.7.0 try again later meaning and 450 4.2.1 requested mail action not taken.
Example wording (illustrative): "421 4.7.0 Try again later."
Classification and action: soft. Retry automatically and slow the send to that provider. Don't count deferrals as hard bounces.
Worked example (illustrative): suppose 6,000 of a 40,000-recipient send defer at one provider within the first hour. Retrying all 6,000 immediately repeats the burst and produces more deferrals. Instead, spread the remaining sends over several hours and check whether the deferral rate falls.
Common mistake: treating a deferral spike as list damage and suppressing the addresses. The list is usually fine; the send rate is the problem.
Bottom line: deferrals are a pacing signal, not a list signal.
What are message-size, catch-all and undetermined bounces?
These three don't fit cleanly into hard or soft. Handling them like ordinary bounces can damage a healthy list.
7. Message too large (552 5.3.4)
What it means: the message exceeded the receiving server's size limit. The address is fine, and retrying the same message won't help.
Example wording (illustrative): "552 5.3.4 Message size exceeds fixed maximum message size."
Classification and action: message-level. Don't suppress the address. Remove or compress attachments and images, and link to large files instead. Limits differ by provider, so check the one that's bouncing.
Tip: attachments are base64-encoded in transit, which adds about a third to their size. A 7 MB PDF becomes roughly 9.3 MB (7 × 4/3) on the wire, so check the encoded size, not the original file.
Where verification helps: it doesn't. The problem is your content, not the recipient.
Bottom line: shrink the message; the address is fine.
8. Catch-all acceptance (no bounce at all)
What it means: catch-all domains accept mail for any recipient at SMTP time, so the server can't confirm that a specific mailbox exists. An invalid address at a catch-all domain may never bounce. It simply sits there, or bounces late, if at all. Your send log will look clean while part of the segment is dead.
Example wording: none. The message is accepted, and there may be no bounce to read.
Classification and action: undetermined until verified. Don't assume valid. Sort catch-all addresses into a Risky segment, and decide who receives them based on engagement. Bounce history is a poor signal here.
Where verification helps: Unlimited Verifier detects catch-all domains and sorts those addresses into Risky. Its deep verification is available for the Risky bucket, which the company states has 99.5% accuracy; that's Unlimited Verifier's own figure, not one we tested. You can check catch-all addresses before deciding how to treat them.
Tip: a catch-all segment that never bounces can still contain dead addresses. Engagement is the signal to use. Send to Risky addresses only if they've opened or clicked recently.
Bottom line: the absence of bounces is not evidence of validity at a catch-all domain.
9. Undetermined bounces (auto-replies and reports with no usable code)
What it means: not everything in a bounce folder is a failure. Out-of-office replies and auto-responders prove the mailbox exists. Other items arrive as delivery status notifications that lack a usable enhanced code, or come from a Mailer-Daemon sender with generic text. The DSN format is defined in RFC 3464.
Example wording (illustrative): "Thank you for your message. I am out of the office until Monday." This is a delivered message, not a bounce.
Classification and action: read the enhanced code in the status part of the notice, or your ESP's category, not the sender name. An out-of-office reply means keep the contact active. A DSN with no code that repeats for the same address should be verified before you decide.
Where verification helps: verification can confirm whether the address looks deliverable, which helps you decide between suppressing and investigating. If Mailer-Daemon messages are filling your inbox, our guide on why you keep getting Mailer-Daemon bounce messages explains the common sources.
Bottom line: read the message before you suppress on it.
Which action fits each bounce type?
| If you see | Do this | Don't do this |
|---|---|---|
| 5.1.1 or 5.1.3 | Suppress, or fix the syntax at the source | Keep retrying |
| 5.1.2 clustered on one domain | Check DNS, then suppress the segment | Suppress individuals one by one |
| 5.7.x blocks | Fix authentication and reputation | Suppress the addresses |
| 4.2.2 repeated 3 times | Treat as hard | Retry indefinitely |
| 4.7.0 or 4.2.1 spikes | Slow the send and spread it out | Purge the list |
| 5.3.4 | Reduce the message size | Change the recipient list |
| No bounce at a catch-all domain | Sort to Risky; segment by engagement | Assume it's valid |
Bottom line: let the code decide the action, and write that mapping down before the next send.
How do you audit bounces and clean the list with Unlimited Verifier?
This process takes one export, one upload and one re-import per list. Plan for the retention windows below.
- Pull your bounce log with raw codes. Use the enhanced status code column if your ESP exports it. Group bounces by code, not by the label your ESP displays.
- Calculate your hard-bounce rate per campaign: hard bounces (5.1.x) divided by recipients attempted.
- Export the full list as CSV, keeping the email column and any tags you need. Keep each file under 10MB.
- Sign up for the Free plan for small lists. Pro is required for API access and lists above 150 emails.
- Upload and verify the list. The email column is detected automatically.
- Compare results with your bounce log. Expect overlap, not equality. Invalid often includes addresses that haven't bounced yet, and some bounced addresses come back Valid because their server doesn't confirm mailboxes.
- Download immediately. Free results are kept for 24 hours and Pro results for 30 days. Export as CSV, Excel or JSON.
- Re-import: suppress Invalid in your ESP, tag Risky for engagement-based sending, and keep Valid. If you automate checks, the email verification API is available on Pro.
- Repeat for new signups before their first send, and re-verify the full list each quarter. This is the core of email verification API and automation for a growing list.
Worked example (illustrative). A campaign goes to 40,000 recipients and produces 520 bounces: 410 at 5.1.1, 60 at 5.1.2, 30 at 5.7.x and 20 undetermined. Check the arithmetic: 410 + 60 + 30 + 20 = 520. The total bounce rate is 520 ÷ 40,000 = 1.3%. The hard-bounce rate counts only 5.1.x: 470 ÷ 40,000 = 1.18%, above the 1% target. Suppress the 470, investigate the 30 block-related bounces at the sending level, and read the 20 undetermined messages before deciding anything.
Which plan fits? On Free, the list needs 267 files of up to 150 emails (40,000 ÷ 150, rounded up). Free allows 25 lists a month, so it can't cover this list in one month. On Pro, lists can hold up to 25,000 emails, so two files of 20,000 cover it, and standard verification is unlimited. Pro is $29/month, or $25/month billed annually. For how per-check and flat pricing compare, see email verification pricing.
Bottom line: one audit means one export, one upload and one re-import, and you need to download results inside the retention window.
What mistakes do teams make with bounce types?
- Trusting the wording over the code. Classify by the enhanced code, or you'll misfile a full mailbox as a hard bounce. Our 10 SMTP error codes every email marketer should know is a useful reference.
- Suppressing blocks. This removes valid readers and hides the reputation problem underneath.
- Retrying hard bounces. A 5.1.1 won't succeed on a second attempt.
- Missing domain-level clusters. A 5.1.2 spike on one domain is one problem, not hundreds.
- Treating "no bounce" as "valid". Catch-all domains hide failures, and mailboxes close after a verification check.
- Letting results expire. Free results are kept for 24 hours. Download every export the same day.
For background on the standards behind these codes, see RFC 5321 and RFC 3463. For sender practices, M3AAWG publishes industry guidance. If you're building a bounce-handling playbook, begin with our SMTP error codes list with meanings and the common soft bounce reasons list.
Bottom line: most bounce mistakes come from classifying on the wrong signal, not from missing data.
Verdict
Bounces are easiest to manage when each type has one rule: suppress hard bounces, retry soft ones with a cap, and fix blocks at the sending level. Add a pre-send check so that invalid and risky addresses are sorted before they produce bounces at all. Unlimited Verifier's standard verification is included on every plan, including Free, which makes it practical to audit and re-check a list as often as your bounce rate requires. If you're choosing a verifier for this work, how to choose an email verifier lays out the criteria.
Bottom line: classify by code, act by type, and verify before you send.
Bounce type quick-reference
| Bounce type | Typical code | Hard or soft | Right action |
|---|---|---|---|
| Nonexistent mailbox | 550 5.1.1 | Hard | Suppress |
| Mailbox full | 452 4.2.2 | Soft | Retry, then suppress on repeat |
| Policy or auth block | 550 5.7.1 / 5.7.26 | Block | Fix sending, don't suppress |
| Throttling | 421 4.7.0 / 450 4.2.1 | Soft | Retry, slow the send |
| Message too large | 552 5.3.4 | Message-level | Reduce message size |
Frequently asked questions
What is the difference between a hard bounce and a soft bounce?
A hard bounce is a permanent failure, usually a 5xx code such as 550 5.1.1 for a nonexistent mailbox, so the address should be suppressed. A soft bounce is a temporary 4xx failure, such as 452 4.2.2 for a full mailbox, and the message can be retried. Classify by the enhanced status code, not the wording.
What does a 550 5.1.1 bounce mean?
A 550 5.1.1 bounce means the recipient mailbox does not exist at the receiving server. It is a hard bounce. Remove the address from your list immediately, because repeated sends to nonexistent mailboxes raise your bounce rate and can harm sender reputation.
What does a 452 4.2.2 bounce mean?
A 452 4.2.2 bounce means the recipient's mailbox is full. It is a soft bounce, so the message can be retried later. If the address keeps returning soft bounces across several attempts, treat it as a hard bounce and suppress it.
How many soft bounces before I stop sending?
A common practice is to treat an address as hard after three consecutive soft bounces. This is a recommendation rather than a universal standard, and platforms differ in their rules. Check your ESP's documentation and align your suppression policy with it.
Should I remove contacts that get a 5.7.1 or 5.7.26 bounce?
Usually no. Codes 550 5.7.1 and 550 5.7.26 indicate a policy or authentication block, such as failed SPF, DKIM or DMARC checks, or content rejected by the receiver. The address is often valid, so fix your sending authentication, reputation or content instead of deleting the contact.
What is a safe hard bounce rate?
Keeping hard bounces under 1% per send is a sensible target. Many ESPs and deliverability guides flag problems around 2%, so aiming for 1% leaves headroom. Track the rate per campaign and per list source to find problem segments early.
Can email verification prevent bounces?
Verification can catch many hard-bounce causes before you send, including syntax errors, invalid domains and nonexistent mailboxes. It cannot catch every case, however, and catch-all domains accept mail at send time, so some failures still appear after sending. Combine pre-send checks with engagement-based list hygiene.
What is a catch-all domain and why does it matter for bounces?
A catch-all domain accepts mail for any address at that domain, including ones that do not exist. Because the server reports success at send time, bounces can appear later or not at all, which makes these addresses hard to judge. Segment them by recent engagement rather than assuming they are valid.
What does a 552 5.3.4 bounce mean?
A 552 5.3.4 bounce means the message exceeds the receiving server's maximum size. It is a message-level problem rather than a bad address, so the fix is to reduce attachment size or remove large images, not to suppress the contact.
Why does a bounce have no error code?
Some bounces arrive as auto-replies or delivery status notifications without a usable code, or the receiving system is nonstandard. Read the raw message headers and body to identify the cause, and classify it once you find a clear code.
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 standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
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.