Article
Top 5 Reasons Emails Hard Bounce (and How to Fix Each One)
By Unlimited Verifier Team ·

Summary
A hard bounce is a permanent delivery failure, most often a nonexistent mailbox reported as SMTP 550 5.1.1. Four of the five main causes are list problems you can fix by verifying and cleaning addresses, while policy rejections such as 554 5.7.1 point to your authentication or sending reputation.A nonexistent mailbox, reported as SMTP 550 5.1.1, is usually the most common reason an email hard bounces, but five distinct causes produce hard bounces, and four of them are list problems you can fix by cleaning addresses. The fifth, a sender-side policy rejection such as 554 5.7.1, reflects your authentication or sending reputation, and no amount of list cleaning will fix it.
This guide is for marketers, list owners, agencies and SaaS teams cleaning large databases for deliverability and email verification compliance and hygiene. It is part of our guide to email bounce codes. Keep the SMTP error codes list with meanings open while you work through your logs.
Quick answer
- Most common cause: a nonexistent mailbox (550 5.1.1), usually from typos, deleted accounts or bad imports. Suppress addresses that fail the mailbox check.
- Domain and account failures (550 5.1.2, 550 5.2.1): a domain with no working mail server is one suppression decision, not hundreds. A disabled mailbox is a decay problem, so pair verification with a sunset policy.
- Malformed addresses (501 5.1.3): a syntax error that almost always starts in your import or signup form. Fix the source file first.
- Policy rejections (554 5.7.1, 550 5.7.26): a sender problem. Fix authentication and complaint rates, and don't delete the recipients.
- Target: keep hard bounces under 1% of each send, and verify new signups weekly.
Which hard bounce reason should you fix first?
Fix the reason that accounts for the most hard bounces in your own logs, starting with the address-level codes that verification can catch before you send. A hard bounce is a permanent failure: the receiving server says the address or domain will not accept mail, so retrying won't help. A soft bounce is temporary, typically a 4xx code such as 421 4.7.0, and your ESP retries it on a normal schedule. For a deeper split, see hard bounce vs soft bounce codes.
| Reason | Typical code | What it means | Can verification catch it before sending? | First fix |
|---|---|---|---|---|
| Mailbox doesn't exist | 550 5.1.1 | Recipient isn't a live mailbox | Usually yes, via the SMTP mailbox check | Suppress Invalid; correct typos only with consent |
| Domain can't receive mail | 550 5.1.2 | No usable mail host for the domain | Usually yes, via domain and MX checks | Retry once, then suppress the domain |
| Mailbox disabled or closed | 550 5.2.1 | Account existed but no longer accepts mail | Often, not always | Suppress; apply a sunset policy |
| Malformed address | 501 5.1.3 | Address fails basic syntax | Yes, via the syntax check | Fix the import or form |
| Policy or reputation rejection | 554 5.7.1, 550 5.7.26 | Your message was refused, not the address | No | Fix authentication, complaints and listings |
Quick picks by situation
- Bounces spiked on the first send after an import: check for malformed addresses and column errors first.
- Bounces grow steadily over months: this is list decay. Verify the full list and add a sunset policy.
- Bounces concentrate on one domain: check for a domain-level failure before touching individual addresses.
- Bounces rise at one provider with 5.7.x codes: treat it as a sending-setup problem before changing the list.
Bottom line: the code tells you whether the problem sits in the address or in your sending, and that decides the fix.
How we compared the five reasons (and limitations)
We ranked the five reasons on four criteria:
- How often they appear in typical bounce logs. Based on public documentation and common bounce patterns, nonexistent mailboxes and list decay come up most often.
- Whether list cleaning fixes them. Address-level problems respond to verification. Sender-side problems don't.
- Risk if mishandled. Some responses, such as suppressing policy rejections or re-mailing a lapsed domain, can cause more damage than the bounce itself.
- Diagnostic clarity. Can you identify the cause from the code and text your ESP returns?
Limitations. This article is based on public documentation and common bounce patterns. It does not rest on a dataset we measured, so treat the worked examples as illustrations to check against your own logs. Bounce text varies by mailbox provider, and many ESP dashboards collapse different codes into one "hard bounce" count, which hides the cause. Verification reduces hard bounces but can't predict every future one, because some mailboxes accept mail at SMTP time and fail later. Accuracy figures from any vendor are that vendor's claims, so test any tool on a sample of your own list.
Bottom line: use these criteria to choose where to start, and check the examples against your own data.
1. The mailbox doesn't exist (550 5.1.1)
RFC 3463 defines 5.1.1 as a bad destination mailbox address: the server recognizes the domain but has no such recipient. Typical causes are typos in the local part or domain, former employees whose mailboxes were deleted, and imports where the wrong column landed in the email field. For the full pattern, see 550 5.1.1 user unknown meaning.
Key signals in your data
- Bounces cluster on a few typo domains such as gmial.com, hotnail.com or yaho.com.
- Bounces come from addresses that were active once and went quiet after a job change.
- A batch of bounces matches one import file or one signup-form change.
How to fix it
Run the list through an SMTP mailbox check before the next send, and suppress the Invalid results in your ESP so they don't return on the next import. Group bounces by domain, because a typo domain shows up as a pattern faster than as individual rows. Don't silently rewrite addresses. If you want to correct "gmial.com" to "gmail.com," confirm it with the subscriber first, since mailing a guessed correction can reach a stranger.
Where verification falls short
Catch-all domains accept mail for any address at SMTP time, so a nonexistent mailbox there may never produce a clean 5.1.1 at all. That's why catch-all results need a separate policy from Invalid addresses. To check a single suspicious address, use the free email checker.
Worked example (illustrative): a 60,000-address list produces 1,800 hard bounces on one send, or 3.0%. If 1,100 of those are 5.1.1 and come from 14 typo domains, you have a concentrated signup-form problem, not a general list-quality crisis.
Bottom line: group 550 5.1.1 bounces by domain, suppress the Invalid results, and never auto-correct addresses without consent.
2. The domain can't receive mail (550 5.1.2)
Code 5.1.2 means the server can't find a usable destination host for the domain. In practice that points to a domain with no working mail server: an expired registration, a domain never set up for email, a typo such as ".con" or ".comm," or a company domain that went dormant when the business closed. The 550 5.1.2 bad destination host pattern is the one to check against your bounce text.
Key signals in your data
- Many bounces share one domain, and every address fails together.
- The bounce text names a host or DNS lookup failure instead of a specific user.
- Failures begin at the same moment across the whole domain.
How to fix it
Separate a real domain failure from a temporary DNS fault. Retry after a short wait, such as one to two days, and suppress the domain if it still fails. One domain decision can remove dozens or hundreds of addresses at once, which is far more efficient than working through each one.
There is one risk many teams miss. A lapsed domain can be re-registered by a third party, and mailing a domain you no longer control means sending to an address you can't vouch for. Suppress it and move on; don't wait for it to recover.
Unlimited Verifier checks domain and MX records as part of every verification run, so a domain with no mail routing shows up in the results before you send.
Worked example (illustrative): a send produces 412 hard bounces. 388 come from 9 domains with no MX records. Suppressing those 9 domains removes 388 addresses in one action, and you retry the remaining 24 individually.
Bottom line: treat a domain-wide failure as one decision, and retry before you suppress.
3. The mailbox is disabled or closed (550 5.2.1)
RFC 3463 defines 5.2.1 as a mailbox that is disabled and not accepting messages. This differs from a mailbox that never existed: the address was real, and the account was turned off. Corporate offboarding is a common cause, and so is a consumer account closed by the provider after long inactivity.
This is the slow-moving reason. Industry commentary describes list decay as a steady loss, but the rate depends heavily on how the list was built. Track bounces by month rather than assuming a fixed annual rate.
Key signals in your data
- Bounces rise gradually across the list instead of spiking after one event.
- Some addresses that bounce had engaged for years.
- Several addresses at one company bounce weeks apart. This usually means individual accounts closed, not that the domain itself stopped working, so check whether the domain still accepts mail before suppressing it.
How to fix it
Suppress the disabled addresses and add a sunset policy. A sunset policy moves subscribers who haven't opened or clicked within a set window into a re-engagement flow, then removes those who don't respond. Windows of 180 or 365 days are common. This is the strongest defense against 5.2.1, because verification alone can't tell you which mailbox will close next month.
Where verification falls short
Some providers accept mail during the SMTP check and bounce it later, so a clean result is not a permanent guarantee.
Worked example (illustrative): a B2B list of 25,000 contacts loses 4% of its mailboxes over a year. That's 1,000 bounces, or roughly 83 a month. A full verification pass every quarter catches each batch of closures within about three months, rather than letting them accumulate for a year.
Bottom line: 5.2.1 is a decay problem, so pair quarterly verification with a sunset policy.
4. The address is malformed (501 5.1.3)
The basic reply code 501 with enhanced code 5.1.3 means the server rejected the address for bad syntax. This is the most preventable reason, and often the most embarrassing, because it usually starts in your own data pipeline.
Common causes include spaces inside an address, missing or doubled @ symbols, trailing commas or semicolons copied from a spreadsheet, double dots, and look-alike characters. A frequent cause in bulk imports is an unquoted comma that splits a name into the email field and shifts every column after it. For real examples of how these look in logs, see examples of hard bounce messages.
Key signals in your data
- Bounces appear on the first send after an import or form change, not gradually.
- The bounced addresses contain visible spaces, stray punctuation or names instead of emails.
- Most failures trace back to one import source or one signup form.
How to fix it
Fix the source first. Validate syntax at entry with a real-time email validation check on signup forms, and confirm the CSV delimiter and quoting before any import. Then run the full file through verification, which checks syntax first, so malformed rows are flagged before they reach your ESP.
Worked example (illustrative): you import 8,000 contacts, and 210 bounce on the first send with 501 5.1.3, a 2.6% rate on that send. Opening the export shows a supplier's file used semicolons instead of commas, so names landed in the email column. The fix is a corrected import, not a list-wide cleanup.
Bottom line: if bounces appear at the moment of import, check the file before you blame the list.
5. The receiving server rejects your message on policy grounds (554 5.7.1, 550 5.7.26)
This is the reason that doesn't belong on a list-cleaning checklist, and misdiagnosing it is the most expensive mistake on this page. A code such as 554 5.7.1 means the receiving server refused delivery on policy grounds. The address may be perfectly valid. The message was refused because of who sent it, how it was authenticated, what it contained or your sending reputation.
Google's email sender guidelines set expectations for bulk senders, including authentication with SPF and DKIM, a DMARC policy, and a spam rate in Postmaster Tools below 0.10%. Google also flags spam rates of 0.30% or higher as a serious problem. Unauthenticated mail to Gmail can be rejected with codes such as 550 5.7.26.
Key signals in your data
- The bounce text mentions authentication, policy, blocked, reputation or a blocklist.
- Bounces cluster at one provider rather than spreading across domains.
- The problem began after a change to your sending domain, authentication or IP address.
How to fix it
Stop, diagnose, then act. Confirm SPF, DKIM and DMARC are correctly published for your sending domain. Review complaint rates and engagement trends. Check blocklists with Unlimited Verifier's free domain blacklist checker, which covers the domain side. Yahoo's sender guidance makes similar points about authentication and complaints. Don't mass-suppress recipients who bounced on a policy code. You would remove real subscribers to solve a problem that sits in your setup.
Where verification falls short
Verification sorts addresses. It can't change how your messages are authenticated or how receiving servers judge your reputation, so this reason needs an investigation, not a cleanup file.
Worked example (illustrative): a spike of 5.7.26 bounces across 30,000 Gmail addresses appears the week after a DMARC change. Suppressing those addresses would remove engaged subscribers. The right response is to fix the authentication record, confirm the bounce rate falls, then resend to the addresses that were blocked.
Bottom line: a policy rejection is a sender problem; fix your setup, and keep the recipients.
How many hard bounces is too many?
Keep hard bounces under 1% of each send. Commonly cited guidance places the warning zone around 2%, so treat anything above 1% as a signal to investigate and anything approaching 2% as urgent. Sources disagree on the exact threshold, and mailbox providers don't publish a single figure we can verify, so we recommend 1% because it leaves headroom.
Calculate the rate as hard bounces divided by emails sent, multiplied by 100, and use the same basis every time. Small sends swing easily: on a 500-address send, five bounces is exactly 1.0%, and one extra bounce moves the rate by 0.2 points. For small lists, judge the rate across the last four sends rather than one.
Bottom line: 1% is the target, 2% is the alarm, and the rate only means something when you calculate it the same way each time.
How do you clean hard bounces step by step with Unlimited Verifier?
This process works for a one-time cleanup and for weekly signups. It assumes you've already grouped bounces by code, which is the step most teams skip.
- Export your bounce log from the ESP. Include the email address, the bounce code and the diagnostic text. If bounces arrive as automated notices in a shared inbox, see why you keep getting MAILER-DAEMON bounce messages to make sure you're capturing the right data.
- Separate the address-level codes. Keep 5.1.1, 5.1.2, 5.2.1 and 501 5.1.3 in one file. Set aside 554 5.7.1 and 550 5.7.26 for a sender investigation, and leave 4xx codes out of the cleanup file entirely.
- Sign up for an account. The Free plan covers small lists. Pro is $29/month, or $25/month billed annually.
- Split large files. On Free, each list holds up to 150 emails. On Pro, each list holds up to 25,000. A 60,000-address list needs three Pro files (25,000 + 25,000 + 10,000). On Free it would need 400 lists, which is more than the 25 lists a month the plan allows.
- Upload your file. Unlimited Verifier detects the email column automatically. Files can be up to 10MB.
- Review the three buckets. Valid stays active. Invalid gets suppressed. Risky results get segmented, and catch-all, disposable and role-based flags are the main reasons to review them.
- Use deep verification on uncertain addresses. The Pro plan includes 25,000 deep verifications a month, and Free includes 750. Spend them on addresses that need a closer look, not on addresses already marked Valid. Unlimited Verifier states 99.5% accuracy for deep verification. That is the vendor's claim, so test it on a sample of your own list.
- Export and download the results. Export as CSV, Excel or JSON. Free results are kept for 24 hours and Pro results for 30 days, so save every file promptly.
- Re-import to your ESP. Add Invalid addresses to your ESP's suppression list so the next import doesn't bring them back. Tag catch-all results for careful sending, and read more about catch-all email verification before deciding how to treat them.
- Measure the next send. A 60,000-address send with 1,800 hard bounces is 3.0%. Your target is 1%, or 600 bounces or fewer on the same volume.
- Automate later. On Pro, you can call the email verification API to check weekly signups in batches of up to 10,000 emails per request, within the 100,000-email monthly API allowance. This is the core of email verification API and automation.
Worked example (cost): the annual Pro plan costs $25 × 12 = $300 a year. Verifying a 60,000-address list quarterly is four full passes, or 240,000 checks, plus 52 weekly signup batches. Standard verification is unlimited on every plan, so the annual cost stays flat as volume grows.
Bottom line: group by code, clean the address-level reasons, and investigate the sender-level ones separately.
How do you choose the right fix for each bounce?
Use this table when a bounce report lands on your desk. Each row pairs what the bounce shows with the likely reason and the action that matches it.
| What the bounce shows | Likely reason | Action |
|---|---|---|
| 550 5.1.1 across many addresses at one domain | Typo domain or deleted accounts | Suppress Invalid; fix the signup form |
| 550 5.1.2 across one domain | No mail server | Retry once, then suppress the domain |
| 550 5.2.1 spread across the list over months | List decay | Verify quarterly; run a sunset policy |
| 501 5.1.3 right after an import | Malformed data | Fix the file; re-import the corrected rows |
| 554 5.7.1 or 550 5.7.26 at one provider | Policy or authentication | Fix authentication and complaints; hold suppression |
| 421 or 450 (4xx codes) | Temporary delay | Not a hard bounce; retry on the normal schedule |
If you're comparing verifiers for this work, the best email verification tools roundup covers the options, and how to choose an email verifier gives a criteria framework. SaaS teams with signup-driven lists should also consider email verification for ecommerce and SaaS workflows, since signup quality drives most 5.1.1 and 501 problems.
Bottom line: the table covers most cases, and any 5.7.x or 4xx code should be routed away from list cleaning.
What mistakes make hard bounces worse?
- Suppressing policy rejections. This removes engaged subscribers and leaves the real problem, your sending setup, untouched.
- Retrying hard bounces. A permanent failure won't succeed on resend, and repeated attempts count against your sending reputation.
- Deleting every Risky address. Catch-all domains often include real readers, so segment them instead of purging.
- Re-importing without suppressing. If Invalid addresses aren't suppressed in your ESP, the next import reintroduces them.
- Treating the bounce total as one number. A 2% rate from 5.1.1 typos needs a different fix from a 2% rate of 5.7.1 blocks. Read the 10 SMTP error codes every email marketer should know before you build your reporting.
- Auto-correcting addresses. A guessed correction can send to a stranger, which creates compliance risk under email verification compliance and hygiene standards.
- Choosing on per-credit price alone. Verifying weekly on a per-credit plan can cost far more than a flat plan over a year. Compare email verification pricing models before you commit.
For a repeatable routine, see email list maintenance best practices. For sender-side guidance, M3AAWG publishes industry best practices for bulk senders, and the RFC 5321 SMTP specification defines the basic reply codes. Enhanced codes such as 5.1.1 are defined in RFC 3463.
Bottom line: most bounce problems get worse when teams act on the total instead of the code.
Verdict
Hard bounces come from five causes, and four of them are list or data problems: nonexistent mailboxes (550 5.1.1), dead domains (550 5.1.2), disabled accounts (550 5.2.1) and malformed addresses (501 5.1.3). The fifth, policy or reputation rejections (554 5.7.1, 550 5.7.26), is a sender problem that needs authentication and complaint work, not a deletion campaign.
Clean the address-level causes with a verification pass before large sends, then run quarterly full-list checks and weekly signup checks. Unlimited Verifier fits that cadence because standard verification is unlimited on every plan and results sort into Valid, Risky and Invalid. Its open-source verification engine on GitHub also lets you read how its checks work rather than trusting a black box.
Bottom line: group bounces by code, fix the list for the address-level causes, and fix your sending for the rest.
Hard bounce fix matrix
| Reason | Code | First fix |
|---|---|---|
| Mailbox doesn't exist | 550 5.1.1 | Suppress Invalid addresses |
| Domain can't receive mail | 550 5.1.2 | Retry once, then suppress domain |
| Mailbox disabled | 550 5.2.1 | Suppress and apply sunset policy |
| Malformed address | 501 5.1.3 | Fix the import or signup form |
| Policy rejection | 554 5.7.1 | Fix authentication and complaints |
Frequently asked questions
What is a hard bounce?
A hard bounce is a permanent delivery failure where the receiving server rejects the message and retrying will not help. Common causes include a nonexistent mailbox or a domain with no mail server. Hard bounces should be suppressed immediately so they don't damage your sender reputation.
What is the most common hard bounce code?
SMTP 550 5.1.1 is usually the most common hard bounce, meaning the mailbox does not exist. It typically comes from typos, deleted accounts or bad imports. Suppress these addresses after the first hard bounce.
Can I resend to a hard bounced address?
No. Resending to a hard bounced address generally wastes sends and can raise complaint and bounce rates. Remove the address from active sending lists and only re-add it if the contact confirms a new, working address.
What is the difference between a hard and soft bounce?
A hard bounce is a permanent failure, while a soft bounce is temporary, usually a 4xx code. Soft bounces are retried by your sending service, and hard bounces are not. Treat repeated soft bounces as hard after a set number of attempts.
What hard bounce rate is acceptable?
Keeping hard bounces under 1% of each send is a common working target for most senders. Higher rates suggest list quality or import problems. Check the rate per campaign and per source list to find the cause.
Why does 554 5.7.1 mean my email was blocked?
554 5.7.1 is a policy rejection, meaning the receiving server refused your message rather than the address. It often relates to authentication, reputation or blocklisting. List cleaning will not fix it, so review SPF, DKIM, DMARC and complaint rates.
Should I delete hard bounced contacts from my CRM?
Suppress them from email sending rather than deleting them, so you keep a record and avoid re-importing them. Note the bounce reason in the contact record. Delete only if your privacy policy or the contact's request requires it.
How often should I verify my email list?
Verify new signups as they arrive, and re-verify the full list on a regular schedule, such as quarterly for active lists. Older lists decay as people change jobs or close accounts, so periodic checks keep hard bounces low.
Does a domain-level hard bounce affect all addresses at that domain?
Often yes. If a domain has no working mail server, every address on it will bounce with 550 5.1.2. Suppress the domain once rather than checking each address individually.
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.