Article
550 5.1.2 Bad Destination Host: What It Means and How to Fix It
By Unlimited Verifier Team ·

Summary
A 550 5.1.2 bad destination host error is a permanent SMTP failure saying the recipient's domain or host cannot receive mail. Treat it as a hard bounce, suppress the address, and check whether the cause is a domain typo, a dead domain, or your own sending setup.A 550 5.1.2 bad destination host error is a permanent failure meaning the sending server could not treat the recipient's domain or host as a valid destination: it doesn't exist, has no working mail routing, or refuses mail entirely. The official enhanced status name is "Bad destination system address" (RFC 3463), and "bad destination host" is the everyday paraphrase. Don't retry these addresses. Suppress them, then find out whether the cause is one typo, one dead domain, or your own sending setup.
This guide is for list owners, marketers, agencies and SaaS teams who see this code in ESP bounce reports or mail server logs. For the full code reference, start with our email bounce codes pillar.
Quick answer
- What it means: 550 is a permanent SMTP refusal. 5.1.2 says the destination domain or host is the problem, not the individual mailbox.
- Should you retry? No. Treat it as a hard bounce and suppress the address.
- Most common cause: a misspelled domain such as
gmial.comoryahooo.comcaptured on a signup form. - Stop and investigate when many unrelated domains fail in the same window. That usually points to your own DNS, relay or sending IP, not to recipients.
- Working rule: group 5.1.2 bounces by domain, and keep hard bounces under 1% per send. Commonly cited warning levels run around 2%, so 1% is a stricter target we recommend, not a published standard.
Quick picks: which 5.1.2 cause should you check first?
- Most common: a domain typo. Check the spelling, then confirm the domain has MX records.
- One domain, many addresses: the domain has lapsed or never had mail routing.
- Many unrelated domains at once: your side (DNS, relay, sending reputation) before the recipients.
- Deliberate refusal: a null MX record, meaning the domain owner has said it accepts no mail.
| Cause | Typical bounce wording | How to confirm | Usual fix |
|---|---|---|---|
| Domain typo | Often "host or domain name not found" (varies by server) | MX lookup returns NXDOMAIN | Suppress; fix at capture |
| Lapsed or unregistered domain | "Domain/host not found" style (varies) | NXDOMAIN; WHOIS shows past expiry | Suppress the whole domain |
| No mail routing (no MX, no A) | Varies | No MX and no A record | Suppress |
| Null MX | Often "domain does not accept mail" (varies) | MX returns 0 . |
Suppress permanently |
| Dead or misconfigured MX host | Varies; some providers say the server "did not accept our requests to connect" | MX points to a hostname with no A record or no SMTP service | Suppress; optional recheck for key contacts |
| Your side (DNS, relay, IP) | Spike across unrelated domains | Your resolver fails; sending IP is listed | Fix your infrastructure first |
| Stale or imported list | Failures cluster on acquired or old domains | Failures begin after an import date | Verify the whole list |
| Malformed domain string | Varies | Missing dot, trailing dot, underscore, raw Unicode | Correct or suppress |
Bottom line: the cause is usually visible in the domain, not the mailbox, so start there.
How we compared (and limitations)
We judged each cause on four criteria:
- Frequency in typical signup-driven lists, described qualitatively. No public dataset we're aware of breaks 5.1.2 down by cause.
- Whether you can confirm it with DNS lookups and your own bounce data.
- Whether the fix is on your side (repair your infrastructure) or the address's (suppress).
- How easily it gets confused with 5.1.1, 5.4.4 or a temporary 4xx error.
Limitations. We have no access to your bounce logs or to any mailbox provider's internal reasons. Bounce wording differs across Postfix, Exim, Microsoft Exchange, Gmail and other systems, so treat the wording column as examples. This guide is based on public documentation, including the RFCs cited here, not on experiments we ran. Where a claim depends on how a specific server behaves, we say so.
Bottom line: use the table to form a hypothesis, then confirm it with DNS and your own bounce data.
What does 550 5.1.2 mean, exactly?
550 5.1.2 is a permanent failure that points at the domain or host in the recipient address, not at the mailbox. The 550 is the SMTP reply code. RFC 5321 lists 550 as "requested action not taken: mailbox unavailable," and the leading digit 5 marks it as a permanent error (RFC 5321).
The enhanced status code, defined in RFC 3463, reads in three parts:
- 5 is a permanent failure.
- .1 is the addressing category.
- .2 is "bad destination system address."
So the receiving side is saying the destination system is not a valid place to deliver mail. That's a different statement from "this person doesn't have a mailbox."
For list hygiene, the practical meaning is simple: this is a hard bounce. Retrying won't help, and the address should leave your active sending list.
Bottom line: 5.1.2 means the domain or host failed, so treat the whole domain as the unit of diagnosis.
How is 5.1.2 different from 5.1.1 and the other codes?
5.1.2 means the host or domain failed; 5.1.1 means the host works but the mailbox doesn't. Confusing the two sends you down the wrong fix. If you see 5.1.1, the domain is reachable and only that person is missing, as explained in our guide to 550 5.1.1 user unknown. If you see 5.1.2, check the domain before the person.
- 5.1.3 is "bad destination mailbox address syntax." Some servers use it for malformed addresses, so read the full text before deciding whether the domain or the local part is at fault.
- 5.4.4 falls in the routing category, "unable to route." Some systems use it for addresses they can't route at all. Check the bounce wording before assuming it matches 5.1.2.
- 550 5.4.1 is a different situation. Microsoft Exchange uses it for "Recipient address rejected: Access denied," a policy rejection, not a missing domain. See 550 5.4.1 recipient address rejected.
- 4.x.x codes are temporary. A brief DNS failure should produce a retry-later response, not a permanent 550. The distinction is explained in 4xx vs 5xx SMTP errors.
For the full set of enhanced categories, see our enhanced SMTP status codes list.
One rule of thumb: if a 5.1.2 address keeps failing after its domain resolves cleanly in DNS, the failure is permanent and the address should be suppressed. If the domain was unreachable at the time, the failure may be temporary, so check again before you conclude anything.
Bottom line: read the domain part first, and don't treat every 5xx as a dead mailbox.
What causes a 550 5.1.2 bounce?
Eight causes cover the patterns that show up most in bounce troubleshooting. We order them by how often they tend to appear in signup-driven lists, based on general practice rather than a published dataset.
1. A typo in the domain name
What's happening: the address was entered with a misspelled domain, such as user@gmial.com, user@yahooo.com or user@hotmial.com. No such domain exists, so there is nowhere to deliver.
How to confirm: a dig MX lookup returns NXDOMAIN, and the domain is usually a near-miss of a major provider.
Fix: suppress the address, and prevent the next one with real-time email validation on your forms. Don't auto-correct at scale. gmial.com probably means gmail.com, but a corrected address reaches a person who never confirmed they wanted your mail. If you correct an address, send a confirmation request first.
Watch for: typos cluster on a handful of domains, which is why grouping by domain finds them fastest.
2. The domain has lapsed or was never registered
What's happening: a company's domain expired, was dropped, or was never registered. This is common when people sign up with a former employer's domain. When a domain lapses, its DNS records usually disappear, and MX lookups fail.
How to confirm: dig MX returns NXDOMAIN, and WHOIS data shows an expiry date in the past. The website may show a parking page.
Fix: suppress every address on that domain. Be careful if the domain comes back later. A re-registered domain may belong to someone else now, and mailing old addresses there is a new risk, not a re-subscription.
3. The domain resolves but has no mail routing
What's happening: the domain exists but publishes no MX records. RFC 5321 describes a fallback: when no MX record exists, the sender may use the domain's A record as the implicit mail host (RFC 5321). If neither MX nor A exists, there is no destination at all.
How to confirm: dig +short MX example.com returns nothing, and dig +short A example.com returns nothing. A website on a separate host is not mail routing.
Fix: suppress. A small business that set up a website but never configured email is a typical case.
4. A null MX record: the domain has opted out
What's happening: RFC 7505 defines a "null MX," an MX record with preference 0 and target .. It tells senders the domain accepts no email (RFC 7505).
How to confirm: dig +short MX example.com returns 0 ..
Fix: suppress permanently. This is one of the clearest signals in this list. The domain owner has published an explicit refusal, so there is nothing to resolve.
5. The MX host exists on paper but is dead or misconfigured
What's happening: the MX record points to a hostname with no A record, or to a server that is offline or refuses SMTP connections. Bounce text varies here, and some providers phrase it as the recipient server "did not accept our requests to connect."
How to confirm: dig +short MX example.com returns a hostname, and dig +short A on that hostname returns nothing. You can also test SMTP from a network that allows outbound port 25, which many residential and cloud networks block.
Fix: suppress. For a high-value B2B contact, a recheck after a few weeks is reasonable, because misconfigured MX records do get repaired. For an ordinary list, suppression is the right call.
6. Your side: a spike across unrelated domains
What's happening: when 5.1.2 appears for many unrelated domains at once, the recipients are rarely the cause. Likely sources include a DNS resolver on your server failing or returning bad answers, a misconfigured relay, or a receiving network refusing your sending IP and reporting it with 5.1.2 wording. Some blocks use separate 5.7.x codes instead; see 554 5.7.1 rejections.
How to confirm: the failing domains have nothing in common, and the spike starts at a single moment. Test name resolution from your sending infrastructure, and check your sending IP against a public blocklist lookup.
Fix: repair DNS, the relay or your IP reputation first. Then retry only the addresses that failed for reasons you have fixed. Don't suppress valid contacts because of your own outage. This is the most expensive mistake in the list, because it quietly removes good subscribers.
7. A stale or imported list
What's happening: the list was migrated from an old platform, purchased, or collected years ago. Domains change hands. After acquisitions, old exports often carry the acquired company's domain, which may be retired.
How to confirm: the bounce rate jumps right after an import, and failing domains cluster around acquired companies or old employers.
Fix: verify the whole list once before the first send after an import, then verify new signups as they arrive. The routine is in our guide to email list maintenance best practices.
8. A malformed domain string
What's happening: the domain part contains something no mail system can resolve. Common examples are a missing top-level domain (user@company), a trailing dot, an underscore (not permitted in standard hostnames under RFC 1123), or an internationalized domain typed as raw Unicode instead of its ASCII form.
How to confirm: scan the domain column for missing dots, doubled dots, underscores and non-ASCII characters. Also check for stray spaces or quotes left by a CSV export, which can corrupt the domain.
Fix: correct it if the intended domain is obvious and you can confirm it. Otherwise suppress.
Bottom line: most causes are visible in the domain, and only item 6 usually means you should pause all sending.
How do you confirm which cause you have?
Two DNS lookups on the domain will identify most 5.1.2 causes. Run dig MX example.com and dig A example.com, then read the result:
- NXDOMAIN on both: the domain doesn't exist (causes 1 and 2).
0 .on MX: a null MX (cause 4).- An MX hostname with no A record: a dead or misconfigured MX (cause 5).
- No MX, but an A record: fallback delivery applies. Check whether that host runs SMTP at all (cause 3 if it doesn't).
- Everything resolves: look at your own side and at list age (causes 6 and 7).
Then apply the heuristic that saves the most time: group by domain, not by address. One address with 5.1.2 is usually a typo. One domain with dozens of 5.1.2 addresses is a domain problem. Many unrelated domains failing on the same day is your problem. Read the full bounce text too, because ESP interfaces often truncate it. If you're working from raw bounces, our guide to mailer-daemon bounce messages shows where the codes appear.
One caution: catch-all domains accept mail at the SMTP stage, so they rarely produce 5.1.2. Their problems tend to surface later, if at all. Don't read a clean 5.1.2 history as proof that a catch-all domain is healthy.
Bottom line: DNS answers plus the domain-level pattern reveal the cause before you change a single address.
How do you clean up 5.1.2 bounces with Unlimited Verifier?
Export the bounces, group them by domain, verify the bounced list, then suppress. For a typical monthly bounce report, this takes about 15 minutes. Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox, so its domain and MX layers are the ones that would surface a domain with no mail routing. It has no native ESP integration, so the workflow is a CSV round-trip or an API call.
Worked example (illustrative, not a benchmark). A list of 48,000 contacts is sent weekly. Over the last 30 days, 905 unique addresses returned 550 5.1.2. Grouped by domain, 412 come from gmial.com, 188 from yahooo.com, and the remaining 305 are spread across 61 other domains.
- Export the bounce log. Pull hard bounces for the last 30 days from your ESP as CSV, keeping the email, bounce code and bounce message columns. If the code isn't a separate column, search the message text for "5.1.2."
- Filter and deduplicate. Keep rows containing 550 5.1.2. You now have 905 unique addresses.
- Group by domain. Add a column with the text after the
@and count by domain. Confirm the pattern: 412 + 188 = 600, and 905 − 600 = 305 across 61 domains. - Sign up for a free account. The Free plan covers a job this size.
- Check the list size against plan limits. Free allows 25 lists a month, each up to 150 emails, plus 750 deep verifications a month. 905 ÷ 150 = 6.03, so you need 7 lists, using 7 of your 25. The full 48,000-contact list would need 320 Free lists (48,000 ÷ 150), far beyond the monthly cap, so it belongs on Pro.
- Upload and verify each file. Upload CSV or Excel up to 10MB. The email column is detected automatically.
- Read the three buckets. Invalid addresses get suppressed. Valid addresses that bounced 5.1.2 in your ESP are a conflict to investigate: check the domain's DNS yourself and reread the ESP bounce text. Verification is a point-in-time check, so don't assume either side is automatically right. Risky results on a domain need separate handling, covered in our note on catch-all email verification.
- Export immediately. Free results are kept for 24 hours and Pro results for 30 days, so download CSV, Excel or JSON before the window closes.
- Suppress in your ESP. Import the Invalid addresses into your suppression list, and suppress confirmed dead domains as whole domains. Otherwise the next import brings them back.
- Handle the rest of the list on Pro. Split the full 48,000 contacts into two files, 25,000 + 23,000 = 48,000, both within the 25,000-per-list Pro limit. Pro costs $29/month, or $25/month billed annually. For ongoing automation, the email verification API on Pro accepts bulk batches of up to 10,000 emails per request, within a 100,000-email monthly allowance. That's the entry point for email verification API and automation.
- Check single addresses with the free email checker when a contact questions a bounce.
- Recheck on schedule. Verify new signups weekly and the full list quarterly.
For the sending side, the arithmetic is useful too. At 48,000 contacts, a 1% ceiling is 480 hard bounces per send. If the 905 addresses above had bounced across four weekly sends, that's roughly 226 per send, about 0.5% of the list. That's a list problem to clean, not an emergency. Run the same check against your own send counts.
Bottom line: group by domain, verify the bounced list first, then suppress the domains that are confirmed dead.
Which fix should you choose?
| Situation | Action | Why |
|---|---|---|
| One address fails 5.1.2 | Check spelling; suppress if the domain has no MX | Usually a typo or one dead address |
| Many addresses at one domain | Confirm with dig; suppress the domain |
The domain is the unit of failure |
| Many unrelated domains the same day | Pause; check DNS, relay and IP reputation | Your side is the likely cause |
| Null MX returned | Suppress permanently | The domain has explicitly refused mail |
| High-value B2B contact, dead MX | Suppress; recheck in a few weeks | Misconfigured MX records do get repaired |
| 5.1.2 spike after an import | Verify the whole imported list | Stale domains are the likely cause |
| SaaS signup form producing typos | Validate at capture; see email verification for ecommerce and SaaS | Prevention beats cleanup |
If you're still choosing a verifier for this work, our guide to how to choose an email verifier covers the criteria that matter for bounce cleanup. If you're weighing a one-off cleanup against an ongoing budget, compare email verification pricing models before committing.
Bottom line: match the action to the scope of the failure: a single address, a whole domain, or your own infrastructure.
What mistakes do teams make with 5.1.2 bounces?
- Retrying 5.1.2 addresses. The code is permanent, so retries add noise and the receiving side will refuse again. The retry logic that's justified applies to 4xx codes, explained in common soft bounce reasons.
- Auto-correcting typos at scale. A corrected domain can route mail to a stranger who never opted in. Confirm first.
- Suppressing your own contacts during your own outage. If the cause is your DNS or relay, the addresses that failed are probably valid.
- Treating one large brand's 5.1.2 as a dead domain. Check DNS first. The failure may be on your side, or a temporary misconfiguration on theirs.
- Verifying once at import and never again. Decay is ongoing. Read the most common email bounce codes and how to fix them alongside your routine.
- Forgetting the re-import. If Invalid addresses aren't added to your ESP's suppression list, the next import restores them.
- Confusing hygiene with consent. Removing bounced addresses is list hygiene, not permission to email anyone else. For the compliance side, see email verification compliance and hygiene. For sender practices, M3AAWG publishes widely used guidance.
Bottom line: most 5.1.2 problems come from acting on an address when the answer lies in the domain or in your own setup.
Verdict
550 5.1.2 means the destination domain or host failed, so it's a permanent, domain-level problem. Suppress the address, group the bounces by domain, and confirm the cause with two DNS lookups. The main exception is a spike across unrelated domains, which points to your own infrastructure. Fix that first, then keep your valid contacts.
For this kind of cleanup, Unlimited Verifier fits well. Its domain and MX checks cover the layer where these failures originate, Free handles a bounce list of a few hundred addresses, and Pro covers the full list with API batching. If you're comparing options more broadly, our roundup of best email verification tools covers the alternatives.
Bottom line: treat 5.1.2 as a domain verdict, not a mailbox verdict, and your list will stay clean.
Cause triage: first check by pattern
| Pattern | First check |
|---|---|
| One domain, many addresses | MX lookup on that domain |
| Single address, common domain | Spelling at signup |
| Many unrelated domains at once | Your DNS resolver and sending IP |
| Failures start after an import | Source and age of the imported list |
Frequently asked questions
Is 550 5.1.2 a hard bounce?
Yes. A 550 5.1.2 is a permanent failure, so it counts as a hard bounce. Do not retry the address. Suppress it so future sends do not repeat the failure and do not damage your sender reputation.
What is the difference between 5.1.1 and 5.1.2?
5.1.1 means the individual mailbox does not exist, while 5.1.2 means the destination domain or host is the problem. With 5.1.2, the server could not treat the domain as a valid mail destination at all.
How do I check if a domain is bad?
Run an MX lookup on the domain using a DNS tool. If it returns NXDOMAIN, the domain does not exist. If it returns a null MX (0 .), the owner has declared that it accepts no mail. Either result confirms the domain is the cause.
Why do I suddenly get many 5.1.2 bounces across different domains?
That pattern usually points to your own side, such as a DNS resolver failure, a broken relay, or a sending IP that is listed on a blocklist. Check your resolver and IP reputation before assuming recipients are at fault.
Can a 550 5.1.2 error be temporary?
Generally no. The 550 code is a permanent failure. However, a DNS problem on your side can mimic it, so if many unrelated domains fail at once, verify your resolver before suppressing addresses.
Should I remove all addresses that bounce with 5.1.2?
Suppress them from future sends. For high-value contacts on a domain that might have a temporary DNS issue, you can recheck the MX record later before deciding to delete. Otherwise, suppression is the safe default.
What is a null MX record?
A null MX record is an MX entry with a preference of 0 and a target of a single dot. It tells senders that the domain accepts no email. Mail to such a domain should be suppressed permanently.
How do I prevent 5.1.2 bounces from signup forms?
Add domain typo detection at capture, flag common misspellings such as gmial.com or yahooo.com, and require a valid domain with MX records. Validating at the point of entry prevents most of these bounces from reaching your list.
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.