Article
Examples of Hard Bounce Messages: 8 Codes and What to Do About Each
By Unlimited Verifier Team ·

Summary
The most common hard bounce messages are 550 5.1.1 (user unknown), 550 5.1.2 (domain or host not found) and 553 5.1.3 (malformed address). A hard bounce is a permanent failure, so the address should be suppressed after one bounce rather than retried. This guide shows eight examples with their wording, meaning and recommended action.The hard bounce messages you'll see most often are 550 5.1.1 ("user unknown," meaning the mailbox doesn't exist), 550 5.1.2 (the domain or host can't be found) and 553 5.1.3 (the address is malformed). A hard bounce is a permanent failure, so the address should be suppressed after one bounce, not retried.
This guide is for marketers, list owners, agencies and SaaS teams who open a bounce report and need to decide what to delete, what to investigate and what is actually a sending problem. It covers eight bounce messages with the wording you'll typically see, what each usually means and the action to take. For the full code reference, start with our email bounce codes pillar.
Quick answer
- Most frequent address-level bounce in typical lists: 550 5.1.1, a mailbox that doesn't exist. Suppress on the first bounce.
- Hard vs. soft: a reply whose enhanced code starts with 5 is permanent; a 4xx reply is temporary. See hard bounce vs soft bounce codes.
- Catchable before sending: most 5.1.x bounces can be caught with a syntax, domain and SMTP mailbox check, except on catch-all domains.
- Not a list problem: 5.7.x bounces (policy, reputation, authentication) usually point to your sending setup. Suppressing addresses won't fix them.
What makes a bounce a hard bounce?
A hard bounce is a permanent delivery failure. The receiving server replies with a three-digit SMTP code, where 5xx means permanent and 4xx means temporary, as defined in RFC 5321. RFC 3463 adds an enhanced status code in the form class.subject.detail. The first digit is the class: 5 is a permanent failure and 4 is a persistent transient failure. Temporary replies such as 421 4.7.0 follow the opposite logic.
A typical bounce line looks like this (Postfix-style wording):
550 5.1.1 <jo.smith@example.com>: Recipient address rejected: User unknown
Read it in three parts: the SMTP reply code (550), the enhanced code (5.1.1) and the provider's sentence explaining the reason. Some exports include only the code, so request the full bounce text from your ESP whenever you can.
Codes are guidance, not a contract. Providers reuse the same code for different causes, and some wrap a policy message in a generic reply. The practical rule is classify by code plus text. The text tells you whether the problem is the recipient, the receiving provider's policy or your own infrastructure.
Bottom line: a 5.x.x code means permanent, but the wording decides what you do about it.
Which hard bounce messages show up most often?
The table below covers the eight examples in this guide. The ordering is a reasoned judgment based on the common causes described in public provider documentation. It is not a measured benchmark, and your own logs will show a different mix.
| Bounce example | Enhanced code | Usually means | Caught by a pre-send check? | Default action |
|---|---|---|---|---|
| User unknown | 550 5.1.1 | Mailbox doesn't exist | Yes, except on catch-all domains | Suppress now |
| Domain or host not found | 550 5.1.2 | Domain has no mail server | Yes (domain/MX check) | Suppress the domain |
| Malformed address | 553 5.1.3 | Invalid address syntax | Yes (syntax check) | Suppress; fix the import |
| Microsoft recipient not found | 550 5.1.10 (also 5.4.1) | Recipient absent from the directory | Often | Suppress now |
| Mailbox disabled or rate-limited | 550 5.2.1 | Deactivated account, or sending pace | Sometimes | Read the text first |
| Mailbox full | 552 5.2.2 | Mailbox over quota | No (changes over time) | Retry within a window |
| Policy or blocking rejection | 550 5.7.1 | Sender reputation, content or blocklist | No | Investigate sender; don't purge |
| Gmail authentication failure | 550 5.7.26 | SPF/DKIM/DMARC failure | No | Fix DNS; don't purge |
Quick picks
- Suppress immediately: 5.1.1, the most frequent address-level bounce.
- Easiest to catch before sending: 5.1.2 and 5.1.3, which are syntax and domain problems.
- Most often misdiagnosed: 5.7.1 and 5.7.26, which look like list problems but usually aren't.
- Often temporary in practice: 5.2.2, despite being classed as permanent.
Bottom line: the table gives you the default; the sections below tell you when to override it.
How we compared (and limitations)
Each example was judged on four criteria, based on public documentation:
- Frequency: how commonly the code and wording appear in provider documentation and ESP bounce references.
- Consistency: whether the code means roughly the same thing across providers.
- Clarity of action: whether the correct response is unambiguous.
- Pre-send detectability: whether a syntax, domain or SMTP mailbox check could catch it before a campaign.
Limitations. This is not based on sending test campaigns, and no public dataset gives a verified ranking of bounce frequency. Providers change their wording, so the examples here are illustrative. Match on the code and the surrounding text in your own logs. Catch-all domains accept mail for any address at SMTP time, so a check can't confirm those mailboxes exist.
Bottom line: use the criteria as a framework, and verify the wording against your own bounce reports.
What does each hard bounce message mean, and what should you do?
1. 550 5.1.1: user unknown (mailbox does not exist)
Typical text: the Postfix-style line shown above. Gmail's wording reads: "The email account that you tried to reach does not exist."
What it means: the domain accepted the connection, but no mailbox exists for that local part. Common causes are typos (jhon@ for john@), former employees and addresses a signup form accepted without any check. For a deeper walkthrough, see 550 5.1.1 user unknown meaning.
Action: suppress on the first bounce and never retry. Repeated attempts to a dead mailbox are a fast way to hurt sender reputation.
Caught before sending? Usually, through an SMTP mailbox check. The exception is catch-all domains, which accept any address at SMTP time and may bounce later. Catch-all email verification sorts those domains into Risky rather than Valid, and for one-off addresses the free single-email checker runs the same kind of check.
Tip: if 5.1.1 dominates your bounces, look at signup sources before blaming the list. A cluster of typos on one form points to a form problem, which real-time email validation at signup fixes better than any cleanup.
Bottom line: suppress on first sight, and treat the volume as a signup-quality signal.
2. 550 5.1.2: domain or host not found
Typical text: "Host or domain name not found," coded 5.1.2 as a bad destination system address.
What it means: the domain doesn't resolve to a mail server. Causes include typo domains (gmial.com, yaho.com), expired domains and companies that dropped their domain after a rebrand or acquisition. See 550 5.1.2 bad destination host meaning for variants.
Action: suppress every address on the domain, not only the one that bounced. A domain that fails for one address is usually dead for all of them.
Caught before sending? Yes. A domain and MX check flags these before a campaign goes out.
Tip: rule out a temporary DNS problem first. Transient lookup failures typically come back as 4xx replies, so a 5.1.2 that repeats across sends on the same domain is a stronger signal. Group bounces by domain, and if dozens of addresses at one domain fail in the same send, you've found a dead domain and a list source to investigate.
Bottom line: a domain-level failure means suppressing the whole domain, then finding where it came from.
3. 553 5.1.3: malformed address
Typical text: "553 5.1.3 Invalid address" or similar. Wording varies, and some servers return 501 for syntax errors.
What it means: the address isn't valid syntax, for example a double @, embedded spaces, a trailing dot or characters the server rejects.
Action: suppress. A malformed address rarely belongs to a reachable person you could contact by correcting a typo.
Caught before sending? Yes, with a syntax check.
Tip: most malformed addresses come from imports, not people. A frequent cause is a CSV column mismatch, where a phone number or name lands in the email field. Check your import mapping before you conclude the list is dirty.
Bottom line: malformed addresses are an import-hygiene signal first and a suppression task second.
4. 550 5.1.10 and 5.4.1: Microsoft recipient not found
Typical text: Microsoft 365 and Exchange Online return codes such as "550 5.1.10 RESOLVER.ADR.RecipientNotFound." You may also see "550 5.4.1 Recipient address rejected: Access denied." Microsoft's Exchange documentation covers these codes.
What it means: Microsoft's directory has no record of the recipient. A 5.4.1 "Access denied" reply often has the same root cause, because edge filtering can reject unknown recipients before they reach a mailbox. It can also reflect a policy block, so read the full text before you decide.
Action: suppress when the text confirms the recipient is missing. A missing directory entry is a permanent state.
Caught before sending? Often. An SMTP check frequently flags missing Microsoft mailboxes, though results depend on the domain's configuration.
Tip: B2B lists concentrate Microsoft-coded bounces, because many business domains run on Microsoft 365 and employees leave often. If your list is mostly corporate, expect this code to rise as contacts churn.
Bottom line: treat "recipient not found" from Microsoft as final, and expect it most in B2B lists.
5. 552 5.2.2: mailbox full
Typical text: Gmail's wording is "The email account that you tried to reach is over quota," coded 552 5.2.2.
What it means: the mailbox exists but is full. RFC 3463 classes 5.2.2 as permanent, but full mailboxes often clear, which is why many ESPs handle the code as soft. The pattern is covered in common soft bounce reasons.
Action: retry within a limited window, and suppress if the address returns the same code across several sends. The window is a policy choice, so set it in your ESP and keep it consistent.
Caught before sending? No. Quota changes over time, so a snapshot check can't predict it.
Tip: don't count a full mailbox as a dead address. Some ESPs classify it as hard and others as soft, so check how yours counts it before comparing bounce rates across tools.
Bottom line: 5.2.2 is hard in the code and often soft in practice, so use a retry window.
6. 550 5.2.1: mailbox disabled, or a rate limit with the same code
Typical text: "The email account that you tried to reach is disabled." Gmail also uses 5.2.1 for rate limits: "The user you are trying to contact is receiving mail at a rate that prevents additional messages from being delivered."
What it means: a disabled account is usually a former employee's inbox that has been deactivated, a typical B2B decay pattern. The rate-limit message carries the same code but means something different: your sending pace is too fast for that recipient, and the problem is temporary.
Action: suppress disabled accounts. For rate-limit messages, slow sending to that provider and retry later. Suppressing engaged subscribers over a rate limit throws away good contacts.
Caught before sending? Sometimes. Disabled accounts are often rejected at the recipient check, but not reliably.
Tip: match on the text, not only the code. A rule that suppresses every 5.2.1 will delete engaged readers during a volume spike.
Bottom line: the same code can be permanent or temporary, so read the sentence before acting.
7. 550 5.7.1: policy or blocking rejection
Typical text: a 550 5.7.1 reply citing policy, spam or a blocked sender. Outlook.com has used wording such as "messages from [IP] weren't sent," which points to the sending IP. Don't confuse this with 554 5.7.1, which uses a different reply code.
What it means: the mailbox exists, but the receiving provider refused the message because of sender reputation, content, authentication or a blocklist. This is not a dead address.
Action: don't purge addresses when 5.7.1 bounces are spread across many recipients. Investigate the sending side first: check your IP and domain against blocklists and review reputation in provider tools. Unlimited Verifier also offers a free domain blacklist checker for this step.
Caught before sending? No. An address check can't see your sending reputation.
Tip: if 5.7.1 hits one provider across many addresses, the cause is almost always on your side. Google's email sender guidelines say to keep the spam rate in Postmaster Tools below 0.10% and to avoid reaching 0.30%. Spam rate is a complaint metric, not a bounce metric, so purging list addresses won't move it.
Bottom line: 5.7.1 is a sender problem wearing a list-hygiene label.
8. 550 5.7.26: Gmail authentication failure
Typical text: "550-5.7.26 Unauthenticated email from example.com is not accepted due to domain's DMARC policy."
What it means: the message failed SPF or DKIM authentication aligned with your domain, under a DMARC policy the recipient enforces. Since Gmail's bulk sender requirements took effect, this has become a common rejection for senders who haven't set up authentication correctly.
Action: fix your DNS. Confirm SPF includes your sending service, DKIM signs with your domain and a DMARC record exists. The addresses themselves are usually fine.
Caught before sending? No. It's a property of your sending infrastructure.
Tip: a sudden 5.7.26 spike after a domain change, a new ESP or a DNS edit is almost always an SPF or DKIM misconfiguration. Check the signing domain before you touch the list.
Bottom line: 5.7.26 is fixed in DNS, not in your list.
How do you act on hard bounces with Unlimited Verifier?
This workflow separates the bounces you can act on now from the list you need to verify before the next send. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so you work from files: export, verify, re-import. You'll need a bounce report with full text and a subscriber export.
- Export your bounce report from your ESP as CSV, including the address and the full bounce reason text. Don't export only the code.
- Group by code and text. Suppress 5.1.x and 5.4.x now. Hold 5.2.2 for a retry window. Hold 5.7.x for investigation.
- Export the full subscriber list so you can check addresses that haven't bounced yet.
- Split the file to fit the per-list cap. On Free, each list holds up to 150 emails. On Pro, each list holds up to 25,000.
- Upload and verify each list. The email column is detected automatically.
- Sort the results. Invalid goes to suppression. Valid stays active. Risky (catch-all, disposable or role-based) goes to an engagement-review segment.
- Spend deep verifications on Risky only. Pro includes 25,000 a month. Addresses already marked Valid don't need them.
- Export as CSV, Excel or JSON and re-import the suppression list and Risky tag into your ESP. Free results are kept for 24 hours and Pro results for 30 days, so download promptly.
Worked example (illustrative figures, not real data). A 40,000-subscriber list produces 480 hard bounces in one send, a 1.2% rate. Suppose the breakdown is 310 of 5.1.1, 95 of 5.1.2 and 75 of 5.7.x.
- Suppress the 405 address-level bounces (310 + 95) now. Hold the 75 5.7.x bounces for investigation, since they likely reflect sender-side policy rather than dead addresses.
- The Free plan won't cover this list. At 150 emails per list and 25 lists a month, Free handles 3,750 emails a month. Your 40,000 would need 267 separate lists, which exceeds the monthly list allowance.
- On Pro, split the file into two uploads of 25,000 and 15,000. Standard verification is unlimited on every plan, so your cost is the subscription: $25 a month billed annually ($300 a year), or $29 a month billed monthly.
Many ESP acceptable-use guidance documents cite about 2% hard bounces as a warning level, though thresholds vary by provider. For a stricter working target, keep hard bounces under 1% per send. That is a practitioner rule of thumb, not a published standard, but it leaves headroom before a provider intervenes. At 1.2%, this list is above it, so the suppression step matters.
For automation, Pro includes API access with batches of up to 10,000 emails per request, which covers weekly signups. The broader email verification API and automation pattern is worth planning before you need it.
Bottom line: suppress address-level bounces now, split the full list to fit the per-list cap, and reserve 5.7.x for a sending-side investigation.
How do you choose a response for each bounce type?
Use this table as the default, and adjust it to your ESP's classification and your sending volume.
| Bounce type | Response | Retry? | Investigate |
|---|---|---|---|
| 5.1.1, 5.1.2, 5.1.3, 5.1.10 | Suppress | No | Signup source, import mapping |
| 5.2.1 (disabled) | Suppress | No | Account churn in B2B segments |
| 5.2.1 (rate limit) | Slow sends to that provider | Yes, later | Send volume and pacing |
| 5.2.2 (mailbox full) | Hold, then suppress if it repeats | Yes, within a set window | Engagement history |
| 5.7.1, 5.7.26 | Hold the campaign and fix the sender | Only after the fix | IP/domain reputation, DNS |
| Risky (catch-all) | Segment by engagement | Not applicable | Opens and clicks |
This policy matters most for email verification for ecommerce and SaaS teams, where transactional and marketing mail often share a domain, so one 5.7.x problem can affect both. If you're choosing a verifier to support this policy, start with how to choose an email verifier and our overview of the best email verification tools. For cost models, see email verification pricing.
Bottom line: the right response depends on the bounce type, so write the policy down before your next send.
Common mistakes
- Suppressing on the code alone. A rate-limit 5.2.1 and a disabled-account 5.2.1 need different responses.
- Purging addresses over 5.7.1 or 5.7.26. These usually reflect your sending setup, and deleting the list won't fix them.
- Retrying 5.1.1 addresses. Repeat attempts to nonexistent mailboxes add to your bounce rate.
- Ignoring domain-level patterns. Ten 5.1.2 bounces at one domain is a dead domain, not ten bad addresses.
- Blaming the list for an import error. A malformed-address spike often starts in a CSV mapping step. For broader code reference, see SMTP error codes with meanings and 10 SMTP error codes every email marketer should know.
- Treating catch-all Valid-looking results as confirmed. Catch-all domains accept mail at SMTP time, which is why the Risky bucket exists.
- Letting results expire. Free results are kept 24 hours and Pro results 30 days, so archive every export.
- Chasing unfamiliar mailer-daemon messages without reading them. If you're seeing bounces you don't recognize, see why you keep getting mailer-daemon bounce messages.
The recurring process behind these steps is covered in our email list maintenance best practices guide. Suppression and retention also carry compliance obligations, which fall under email verification compliance and hygiene. For the legal baseline, see the FTC's CAN-SPAM compliance guide, and for broader sender practice, M3AAWG publishes industry guidance.
Bottom line: most bounce-handling errors come from reading the code without the text.
Verdict
Hard bounces are permanent failures, but not every hard bounce means a dead address. The 5.1.x family (user unknown, domain not found, malformed address and Microsoft recipient not found) should be suppressed on the first hit. The 5.7.x family points to your sending setup, and treating it as list hygiene wastes good addresses while leaving the real problem in place. Mailbox-full and rate-limit messages sit in between and need a retry window, not a blanket rule.
Start with the bounce text, not only the code. Then verify the full list before the next send. Sign up to run your first list with Unlimited Verifier, which catches address-level failures and sorts catch-all domains into Risky.
Bottom line: suppress what's dead, fix what's yours, and retry what's temporary.
Hard bounce triage
| Bounce | Enhanced code | Action |
|---|---|---|
| User unknown | 550 5.1.1 | Suppress now |
| Domain not found | 550 5.1.2 | Suppress domain, verify MX |
| Malformed address | 553 5.1.3 | Suppress, fix import |
| Policy or reputation | 5.7.x | Check authentication and blocklists, not the list |
Frequently asked questions
What is a hard bounce?
A hard bounce is a permanent email delivery failure. The receiving server returns a 5xx SMTP reply, such as 550, indicating the message will never be accepted for that address. Hard bounces should be suppressed immediately rather than retried.
What is the most common hard bounce message?
The most common address-level hard bounce is 550 5.1.1, meaning the mailbox does not exist. In typical lists it appears more than other permanent codes, though your own logs may differ. Suppress the address after the first occurrence.
What does 550 5.1.2 mean?
550 5.1.2 means the domain or host could not be found, usually because the domain has no mail server or its DNS records are missing or wrong. Suppress the whole domain if many addresses share it, and verify the domain's MX records.
What does 553 5.1.3 mean?
553 5.1.3 indicates the recipient address is syntactically invalid, such as a missing @ sign or illegal characters. Fix the source data or import error and suppress the malformed address; retrying will never succeed.
Is a 5.7.x bounce a hard bounce?
Yes, a 5.7.x enhanced code is a permanent failure, but it usually reflects policy, reputation or authentication rather than a bad address. Removing addresses won't resolve it. Check SPF, DKIM, DMARC and blocklist status instead.
Should I retry a hard bounce?
No. Retrying a hard bounce wastes sending reputation and can hurt deliverability. Remove the address from active sends after one hard bounce, and only investigate if many unrelated addresses bounce with the same message.
Can I prevent hard bounces before sending?
Many 5.1.x bounces can be caught with syntax checks, domain and MX lookups, and SMTP mailbox verification. Catch-all domains accept any address, so verification cannot confirm those mailboxes exist.
What is the difference between a hard and soft bounce?
A hard bounce is permanent and starts with 5 in the enhanced code, while a soft bounce is temporary and starts with 4. Soft bounces, such as a full mailbox, may succeed on retry, but hard bounces should not be retried.
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.