Article
550 5.1.1 User Unknown: What It Means and How to Fix It
By Unlimited Verifier Team ·

Summary
A 550 5.1.1 "user unknown" bounce means the receiving server permanently rejected the message because the mailbox does not exist there. Retrying will not help, so suppress the address unless you can confirm a correct spelling. Checking the pattern across your bounce export shows whether the cause is your list, your source, or the recipient's provider.A 550 5.1.1 "user unknown" bounce means the receiving mail server permanently rejected your message because the recipient mailbox does not exist on that server, which makes it a permanent failure. Retrying won't help. Correct the address only if you can confirm a typo, and suppress it otherwise.
This guide is for marketers, list owners, agencies and SaaS teams who see 5.1.1 bounces in an ESP report or mail log and need to know whether the cause is their list, their source or the recipient's provider. It covers six causes, how to tell them apart, and a cleanup workflow using Unlimited Verifier, a bulk tool that checks syntax, domain/MX records and the SMTP mailbox, then sorts every address into Valid, Risky or Invalid. For the broader code family, start with our email bounce codes pillar.
Quick answer
- What it means: the mailbox isn't present on the receiving server, and the 5.x.x class makes the failure permanent.
- What to do: stop sending to that address. Correct it only when you can confirm the right one.
- What to check first: whether one address bounced or a cluster did. A cluster of valid-looking addresses at one provider points to a sending or policy problem, not dead addresses.
- How to prevent it: verify addresses at capture and re-check the full list on a schedule.
- Recommended tool: Unlimited Verifier, which sorts a bounce export into Invalid (suppress), Risky (segment) and Valid (investigate if it bounced).
Which cause of a 550 5.1.1 bounce should you check first?
Start with the pattern across your bounce export, not the single address. One 5.1.1 tells you little. A cluster tells you which cause to test first.
- One address, obvious misspelling: a typo in the mailbox name.
- Several addresses at one company domain, all previously engaged: an account deleted after an employee left.
- Odd or patterned names, a burst from one signup source: an address that never existed.
- Bounces that arrive hours or days after the send: a catch-all domain that accepted mail and later rejected it.
- Valid-looking addresses bouncing together at one provider in one window: provider-side rejection worded as "user unknown."
- Addresses that look right in a spreadsheet but fail in the log: hidden characters or formatting.
| Cause | Typical pattern | Permanent? | Fix | Does pre-send verification catch it? |
|---|---|---|---|---|
| Typo in mailbox name | Single address, obvious misspelling | Yes, for that address | Correct only if confirmed; otherwise suppress | Usually, through the SMTP mailbox check |
| Account deleted | Several addresses at one company domain | Yes | Suppress individuals; re-acquire contact | Often, if re-checked after the deletion |
| Address never existed | Patterned names, one bad source | Yes | Suppress; add double opt-in | Usually, at upload |
| Catch-all domain | Bounce arrives after the send | Yes, once discovered | Move to Risky; engagement-based sending | Partly: flagged as catch-all, not confirmed |
| Provider policy | Valid addresses bounce together | Not a list problem | Pause; check reputation | Not by itself |
| Formatting | Stray spaces, smart quotes, pasted characters | Yes, for that string | Trim and retype | Usually, via the syntax check |
Bottom line: the pattern tells you the cause, and the cause tells you whether the fix is to suppress, correct or pause.
How do you read a 550 5.1.1 bounce, part by part?
The code has two layers. 550 is the basic SMTP reply code. The first digit, 5, is a permanent failure class, as defined in RFC 5321. 5.1.1 is the enhanced status code from RFC 3463: class 5 (permanent), subject 1 (addressing), detail 1 (bad destination mailbox).
The neighboring codes help you rule things out. 5.1.2 indicates a bad destination system, typically a domain that doesn't resolve, and 5.1.3 indicates bad mailbox address syntax. If your bounces show 5.1.2, look at the domain. If they show 5.1.3, look at the formatting.
Providers add their own wording and sometimes their own sub-codes. Gmail's wording has been along the lines of "the email account that you tried to reach does not exist." Microsoft 365 commonly uses 550 5.1.10 for recipient-not-found, which we cover in our Office 365 NDR bounce codes list. The meaning is the same even when the text differs.
Don't confuse 5.1.1 with a temporary failure. A 452 4.2.2 mailbox full bounce is a 4xx error and should be retried later. Our 4xx vs 5xx SMTP errors guide explains the split, and the enhanced SMTP status codes list decodes the rest.
Bottom line: the leading 5 makes a 5.1.1 permanent, so suppress the address rather than retrying it.
How we compared (and limitations)
We grouped the six causes by four criteria: how distinctive the bounce signal is in an export, whether the sender can act on it, whether a pre-send verification check is designed to catch it, and how the pattern shows up in a bounce log over time.
Limitations. This analysis draws on public documentation (the RFCs above and provider sender guidance) and common operational practice. It does not use any receiving server's logs, and provider wording changes without notice. The "pre-send catches it" column describes what SMTP-level checks are designed to detect, not a guarantee. Accuracy figures quoted for any vendor, including Unlimited Verifier's stated 99.5% for deep verification, are the vendor's own claims, so test them on your own list. For tool-by-tool comparisons, see our guide to the best email verification tools.
Bottom line: treat the causes below as patterns to test against your own data, not a diagnosis you can read from one bounce line.
Which six causes produce a 550 5.1.1 bounce, and how do you fix each?
1. A typo in the mailbox name
The local part, the text before the @, is misspelled: "jhon.smith" for "john.smith," or a doubled letter. A typo in the domain usually produces a different code, often 5.1.2, so a 5.1.1 points you at the local part.
Signs it's this cause: a single address at a busy, real domain, with no pattern across the list. The address was probably typed by hand, either by the subscriber or by someone entering it from a phone call or business card.
Fix: don't guess the "more likely" correction. Changing "jhon.smith" to "john.smith" can send your message to a stranger if the second address is a different person's mailbox. Correct the address only when you can confirm it from the source, such as a signed form or a reply from the person, then verify it before sending. Otherwise suppress it.
Can verification catch it? Usually. The SMTP mailbox check asks the receiving server whether the mailbox exists, which is the test that exposes a misspelled local part.
Tip: a double opt-in step at signup catches most typos before they enter your list, because the subscriber has to click a link sent to the address they typed.
Bottom line: a single typo is a one-address fix, and the only safe correction is a confirmed one.
2. An account deleted after someone left
The mailbox was real and was removed when the employee left. This is the cause where your list was once correct and then decayed.
Signs it's this cause: several addresses at the same company domain bounce in one send, and those contacts were engaged in the past. B2B lists commonly decay through job changes, so this pattern is typical there.
Fix: suppress the individual bounced addresses, not the whole domain. Other staff at that company may still be reachable, and blocking the domain removes live contacts. If the relationship still matters, re-acquire the contact through a new, consented source, such as a current contact on the company's website or a response to a relevant email.
Can verification catch it? Often, if you re-check before each send. A list verified six months ago can still hold addresses that were removed since, so the check has to run on the current list.
Tip: group bounces by domain in your export. A cluster at one company is a deleted-account signal. A cluster across many companies usually points elsewhere.
Bottom line: suppress the people, keep the company, and schedule re-checks because decay is continuous.
3. An address that never existed
The address was typed by a bot, scraped, bought from a list broker or entered during signup abuse. It was never a working mailbox.
Signs it's this cause: test-style addresses, patterned or random names, disposable domains, or a burst of bounces tied to one signup source or import file. The bounce timing matters here: a burst that starts on the same day as a particular import or form change is the strongest signal.
Fix: suppress these, add double opt-in to the source, and consider blocking known disposable domains at the form. If one source produces most of your 5.1.1 bounces, fix the source before you clean the list, or the list will refill. Our guide to real-time email validation explains how to check at the point of entry. This is the cause where email verification for ecommerce and SaaS signup flows pay off most.
Can verification catch it? Yes. Syntax, domain/MX and SMTP mailbox checks flag these before a send. Unlimited Verifier also flags disposable and role-based addresses, which adds a second signal for these records.
Tip: sort your bounces by import date or signup source before doing anything else. The source column usually explains more than the address does.
Bottom line: if the bounces cluster by source, the source is the problem.
4. A catch-all domain that bounces later
Some receiving servers accept mail for any address during the SMTP conversation. Your system logs a successful handoff, then the mailbox is discovered not to exist, and a 5.1.1 arrives as a separate non-delivery report (NDR) hours or days later.
Signs it's this cause: bounces that appear after the send rather than during it, concentrated at certain domains. If your ESP shows delivery as successful and then a later bounce for the same address, consider this cause first.
Fix: treat catch-all addresses as Risky. Send to them only if they have engaged recently, and reserve deep verification for the segment where the decision matters. A basic SMTP check on a catch-all domain can't confirm that a specific mailbox exists, which is exactly why the category exists.
Can verification catch it? Partly. Unlimited Verifier detects catch-all email verification domains and routes them to Risky rather than passing them off as Valid. It doesn't confirm the individual mailbox, so treat Risky as a decision to make, not a verdict.
Tip: don't purge every Risky address. Many catch-all domains belong to real companies with real readers. Segment them by recent engagement instead.
Bottom line: catch-all bounces are a delayed signal, so the fix is to stop treating "accepted" as "delivered to a real person."
5. A provider rejecting your mail with "user unknown" wording
Some receiving systems use user-unknown wording when they reject mail for reputation or policy reasons, not because the mailbox is gone. This is the cause most often misdiagnosed, because the code looks like a list problem.
Signs it's this cause: addresses that engaged last month bounce together, many at one provider in the same window, and the same addresses accept mail from other senders. Check whether the bounces started after a change in your sending, such as a new domain, a new IP, a spike in volume or a template change.
Fix: pause rather than resend in bulk. Check your sending domain against blocklists using Unlimited Verifier's free domain blacklist checker, and review your bounce and complaint rates. For Gmail traffic, Google Postmaster Tools is the diagnostic to use. Google's bulk sender guidelines set spam-rate thresholds that bulk senders should monitor, and M3AAWG publishes sender best practices that apply across providers.
Can verification catch it? Not by itself. An address check tells you about the mailbox. It can't tell you that your reputation is the problem, and re-verifying a valid-looking list will keep returning "Valid" while the rejections continue.
Tip: a sudden cluster of 5.1.1 bounces on addresses that previously received mail is a reason to investigate your sending. Purging your list in response usually removes good contacts and fixes nothing.
Bottom line: if valid addresses bounce together at one provider, diagnose your sending before touching the list.
6. Hidden characters and formatting
A trailing space, a non-breaking space, smart quotes or a pasted invisible character changes the address string. The address looks correct in a spreadsheet and fails in the log.
Signs it's this cause: the address reads correctly to a human but fails in the NDR, often after copy-paste from a document, email signature or web form. A single bad row is common; a cluster from one import file is a clear sign.
Fix: trim whitespace, replace smart quotes, retype the address and re-verify. Check for non-ASCII characters if your list is international. Some receiving systems reject unusual or internationalized address formats, so verify those separately.
Can verification catch it? Usually. Unlimited Verifier's checks include syntax, so a cleaned CSV will surface many formatting problems before a send. Addresses that pass syntax can still fail on the mailbox check, so treat clean formatting as necessary, not sufficient.
Tip: normalize the email column (trim whitespace, lowercase the domain) in your export before upload. Lowercasing the domain is safe; lowercasing the local part is a common assumption that some providers treat as case-sensitive in principle, so keep the original local-part case if your source uses it.
Bottom line: formatting failures are the cheapest to fix and the easiest to prevent at the import step.
How do you clean up 550 5.1.1 bounces with Unlimited Verifier?
This workflow turns one bounce export into a suppression list and a re-verified sending list. It works on the Free plan for small exports and on Pro for larger ones.
- Export the hard bounces. From your ESP or mail log, export all hard bounces from the send (5.x.x codes). Keep a working copy with the code column, so you can split 5.1.1 from the rest afterward.
- Group by domain. Count bounces per domain. A cluster at one company or provider changes how you interpret the results.
- Note the retention window. Free results are kept for 24 hours and Pro results for 30 days, so download promptly.
- Sign up for a free account. The Free plan allows 25 lists a month of up to 150 emails each, plus 750 deep verifications a month.
- Upload and verify the list. Upload a CSV or Excel file up to 10MB. The email column is detected automatically.
- Read the three buckets. Invalid: suppress permanently. Valid: if these bounced, investigate the cluster rather than assuming the check was wrong. Risky: catch-alls, disposables and role-based addresses go to a segment.
- Export and archive. Download as CSV, Excel or JSON before the retention window closes.
- Suppress, then re-import. Add Invalid addresses to your ESP's suppression list first. Re-importing without suppressing brings them back.
- Automate the future (Pro). The email verification API supports single checks and bulk batches of up to 10,000 emails per request, within a 100,000-email monthly allowance. This is the basis of email verification API and automation for signup flows.
Worked example (illustrative figures). A 60,000-address list produces 1,380 hard bounces from one send, a 2.3% hard-bounce rate. Many ESPs and deliverability guides use roughly 2% as a warning line. Our email list maintenance best practices target under 1%, which for this list means no more than 600 hard bounces. Assume 1,120 of the 1,380 carry 5.1.1 and 260 carry other 5.x.x codes.
- On Free, all 1,380 rows: 1,380 ÷ 150 = 9.2, so 10 lists. That fits within the 25-list monthly cap, but results expire after 24 hours, so download the same day.
- On Free, only the 1,120 5.1.1 rows: 1,120 ÷ 150 = 7.5, so 8 lists.
- On Pro: all 1,380 rows fit in one file, well under the 25,000-per-list cap, with results kept for 30 days.
- Outcome: suppress the 1,120 addresses that come back Invalid. Don't assume every 5.1.1 row returns Invalid; some may return Risky (catch-all) or Valid (provider-side). Those results decide the next action, which is why the Valid bucket matters as much as the Invalid one.
For context on how pricing models differ across tools, see email verification pricing.
Bottom line: export, verify, suppress, re-import, then automate the check for new addresses.
How should you choose a fix for your 550 5.1.1 situation?
Match the first action to the pattern you found in the export.
- One address, and you can confirm the correct one: correct it, verify it, send once.
- One address, no confirmation: suppress it.
- A cluster at one company: suppress the bounced individuals, then look for a current contact through a consented source.
- Bounces from one signup source or import file: fix the form or the import first, then clean the list.
- Bounces at catch-all domains: move them to Risky and segment by engagement.
- Valid-looking addresses bouncing together at one provider: pause, check reputation and blocklists, and confirm your sending hasn't changed. If your current checks keep passing these addresses, reassess your criteria using how to choose an email verifier.
- Formatting-related failures: clean the export and re-verify.
Bottom line: the fix depends on the cause, so identify the cause before you act.
What mistakes make 5.1.1 bounces worse?
- Retrying a 5.1.1. It's a permanent failure, so retries add noise and can hurt your sending reputation.
- Purging a whole domain without checking. You may remove live contacts at a company that still has other valid staff.
- Guessing corrections. A plausible-looking address may belong to someone who never opted in.
- Re-importing without suppressing. The next import brings the bounced addresses back.
- Treating Valid as proof of engagement. A valid mailbox that hasn't opened in a year still hurts your metrics. Run a sunset policy alongside verification.
- Buying lists to replace bounces. Purchased lists raise email verification compliance and hygiene concerns, and verification doesn't make them lawful. The FTC's CAN-SPAM compliance guide is the starting point for US rules on commercial email.
- Letting Free results expire. Save every export within 24 hours.
- Misreading a 4xx as a 5.1.1. Temporary errors are a different problem, covered in our common soft bounce reasons list.
For a fuller set of troubleshooting steps, see our most common email bounce codes and how to fix them guide. If you want the step-by-step recipient fix, read how to fix 550 5.1.1 recipient address rejected. Our 550 5.7.1 message rejected guide and 550 5.4.1 access denied guide cover the policy responses you may see alongside it. If NDRs keep arriving with no clear source, our article on why you keep getting mailer-daemon bounce messages covers the back-end patterns.
Bottom line: most bounce problems come from skipping the diagnosis step, not from the tool.
Verdict
A 550 5.1.1 bounce means the mailbox doesn't exist at the receiving server, and it's permanent. Suppress the address, correct it only when you can confirm the right one, and treat a cluster of valid-looking bounces as a sending problem to investigate.
For the list side of the cleanup, Unlimited Verifier's syntax, domain/MX and SMTP mailbox checks, catch-all detection and Valid/Risky/Invalid sorting map directly onto the causes above. Its stated 99.5% accuracy for deep verification is the vendor's own claim, so test it on a sample of your own export before relying on it. Start with a free email checker run on a few bounced addresses, and move to a full export once the workflow is clear.
Bottom line: diagnose the cause first, then use verification to stop the same bounce from recurring.
Triage by bounce pattern
| Pattern in export | Likely cause | Action |
|---|---|---|
| One address, obvious misspelling | Typo | Correct if confirmed, else suppress |
| Several addresses at one company | Account deleted | Suppress; re-acquire contact |
| Patterned names from one source | Never existed | Suppress; add double opt-in |
| Bounces hours or days after send | Catch-all domain | Move to Risky; engagement-based sending |
| Valid addresses bounce together at one provider | Provider policy | Pause; check reputation |
| Looks right in sheet, fails in log | Formatting | Trim and retype |
Frequently asked questions
Should I retry a 550 5.1.1 bounce?
No. A 550 5.1.1 is a permanent failure, meaning the receiving server has said the mailbox does not exist. Retrying the same address will get the same rejection. Stop sending to it, and only correct the address if you can confirm the right spelling.
What does 5.1.1 mean in an SMTP error?
The 5.1.1 enhanced status code means the recipient address was rejected because the mailbox is unknown. The first digit 5 marks a permanent failure, and 550 is the SMTP reply code. Together they tell the sending server not to retry.
Is 550 5.1.1 the same as 550 5.1.0?
They are close but not identical. Both are permanent recipient-related rejections in the 5.1.x family. Wording and enhanced codes vary by provider, so check the full bounce text to see which specific rule the receiving server applied.
Can a 550 5.1.1 bounce be caused by my own server?
Sometimes. If many valid addresses at one provider bounce together in a short window, the provider may be rejecting your mail for policy or reputation reasons while using user-unknown wording. Check your sending reputation and whether the bounces cluster.
How do I know if a domain is catch-all?
A catch-all domain accepts mail for any address, so a single test cannot confirm a mailbox. Verification tools typically flag these as risky rather than valid. Bounces that arrive hours or days after sending often reveal a catch-all domain.
Should I remove all addresses that get a 5.1.1 bounce?
Suppress them from active sending, which is the safe default. Keep a record so you do not re-import them. Correct an address only when you can confirm a typo, such as a clear misspelling of a known domain.
How do I prevent 550 5.1.1 bounces in future campaigns?
Verify addresses at the point of capture using syntax, domain and mailbox checks, and re-check the full list on a regular schedule. Add double opt-in for new signups, and remove hard-bounced addresses automatically from your sending lists.
Why do addresses look correct but still bounce?
Hidden characters, stray spaces, smart quotes or pasted formatting can make a valid-looking address invalid to the mail server. Trim and retype the address, then run it through a syntax check before sending.
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.