Article

How to Fix 550 5.1.1 Recipient Address Rejected Errors

By Unlimited Verifier Team ·

Diagram showing a 550 5.1.1 recipient address rejected bounce flowing from sender to a receiving server that finds no mailbox, leading to address suppression.

Summary

A 550 5.1.1 "recipient address rejected" bounce is a permanent failure meaning the receiving server does not have that mailbox. Suppress the address immediately, never retry it, and check whether bounces cluster by domain or point to your own configuration. Verify the rest of your list before sending again.

A 550 5.1.1 "recipient address rejected" bounce is a permanent (hard) failure: the receiving mail server has refused your message because that mailbox does not exist there. Fixing it means suppressing that address for good, finding out how it reached your list, and verifying the rest of the list before you send again.

Quick answer

For the full code map, see our email bounce codes guide. This article covers 5.1.1 specifically.

What does 550 5.1.1 actually mean?

A 550 5.1.1 is a permanent rejection that says the destination mailbox is invalid. The 550 is the SMTP reply code. RFC 5321 defines 5xx replies as permanent failures. The 5.1.1 is the enhanced status code, which RFC 3463 defines as "bad destination mailbox address." Our enhanced SMTP status codes list shows how the enhanced codes are structured.

Two details matter in practice:

Bottom line: 5.1.1 means "this mailbox is gone or never existed." The text after the code tells you which.

Is 550 5.1.1 a hard bounce, and can the address ever come back?

Yes, 550 5.1.1 is a hard bounce, and you should never retry it. A soft bounce such as a full mailbox (452 4.2.2, covered in our 452 4.2.2 mailbox full guide) is worth retrying later. A hard bounce is not, because the address will keep failing.

An address can occasionally come back if someone re-creates the mailbox. Treat it as dead until the person re-confirms through a channel they've consented to. Retrying in the meantime generates failed attempts that mailbox providers can read as poor list hygiene. The usual culprits are not the ESP itself but other tools: a CRM workflow that re-queues failed records, a self-hosted relay with aggressive retry settings, or an automation that treats every 5xx as temporary. Check whether your platform suppresses hard bounces automatically. If it doesn't, add that to your fix list.

Does a 5.1.1 bounce hurt your sender reputation? It counts toward your bounce rate, and a cluster of them on one send can trigger a review. A single bounce is not a reputation event. A wall of them is.

This table separates 5.1.1 from the codes it is most often confused with:

Code Meaning (RFC 3463 unless noted) Retry? What to do
5.1.1 Bad destination mailbox address No Suppress the address; verify the rest of the list
5.1.2 Bad destination system address (host or domain) No Check the domain's MX and DNS; often a retired domain
5.1.3 Bad destination mailbox address syntax No Correct the typo or remove the address
5.1.6 Destination mailbox has moved No Suppress; contact the person only through a consented channel
5.7.1 Delivery not authorized, message refused Not as a list fix Usually a reputation or policy block. See 550 5.7.1 how to fix
4.2.2 Mailbox full (soft) Yes, later Retry on your normal schedule

Our common soft bounce reasons list explains which temporary failures deserve a retry, and 4xx vs 5xx SMTP errors explains the broader distinction.

Bottom line: The code says the address is permanently refused. The damage comes from what happens to that address next.

Why do valid-looking addresses return 550 5.1.1?

Most 5.1.1 bounces come from four causes, and each leaves a different fingerprint in your data.

  1. Deleted or closed mailboxes. Former employees' work addresses and inactive free accounts are removed on the provider's schedule, not yours. In many B2B lists this is a major source, and it grows every year a list sits untouched.
  2. Retired or acquired domains. When a company changes domains or is acquired, the old domain often stops accepting mail. The fingerprint is a cluster of bounces on one domain.
  3. Typos and sloppy capture. Entries like gmial.com or yaho.com come from forms and manual entry. A typo domain that doesn't exist usually fails at the domain level, often with a 5.1.2 code. A typo domain that exists and accepts everything produces no bounce at all, which is more dangerous because you never see the failure.
  4. Your own configuration. If the bounced addresses sit on your own domain, or your MX records changed recently, the fault may be yours. A 5.1.1 on every address at a domain you control points to a recipient-table or migration error, not a list problem.

A caution from practice: some providers return a generic 5.1.1 to block senders or deter address harvesting. A sudden wall of 5.1.1 across a list that was previously healthy can be a reputation problem wearing a "user unknown" label. Check the pattern before you assume the list is at fault. Microsoft 365 uses its own wording for a missing recipient. Its 550 5.1.10 "recipient not found" is a Microsoft-specific extension rather than an RFC 3463 code, and we cover it in our Office 365 NDR bounce codes list. A 550 5.4.1 "recipient address rejected: access denied" is a different failure that usually comes from recipient restrictions, so see our 550 5.4.1 guide before treating it as a dead address.

Bottom line: Domain clusters point to retired domains, scattered bounces point to decay or typos, and bounces on your own domain point to configuration.

How do you diagnose a 550 5.1.1 bounce in five minutes?

Group the bounces instead of reading them one by one. These five checks cover most situations.

  1. Filter for 5.1.1 only. Export the bounce report from your ESP, or search your mail server logs for 5.1.1. Keep 5.7.1 and 4.x codes separate, because they need different fixes. If your bounce notices arrive as automated system emails, our guide to why you keep getting MAILER-DAEMON bounce messages explains where they come from.
  2. Sort by domain. If the top ten domains account for most of the bounces, treat it as a domain-level problem. A scatter of single-address bounces points to decay or typos.
  3. Check DNS for the top domains. Run dig +short MX example.com. An empty answer, with no fallback A record, means the domain isn't receiving mail at all.
  4. Check your own domain. If your domain appears in the top list, review your MX records and recipient settings before anything else.
  5. Spot-check a few addresses. Run three or four through the free email checker. A Valid result on an address that just bounced deserves investigation, not dismissal. The mailbox may have been removed after the check, or the domain may behave differently at send time.

Bottom line: Five minutes of grouping tells you whether to fix a domain, fix your setup, or clean the list. Only the last one needs a full verification run.

How do you fix a 550 5.1.1 bounce, step by step?

Follow this sequence. The order matters because verification only makes sense after you've stopped the damage and ruled out your own configuration.

  1. Stop sending to failed addresses across every tool. Confirm that hard bounces are suppressed in your ESP, CRM and automations, not just in the dashboard you're looking at.
  2. Diagnose the pattern. Use the five checks above and write the cause in one sentence.
  3. Fix your own setup if it's involved. No amount of list cleaning helps a broken recipient table.
  4. Suppress every 5.1.1 address permanently. Keep a copy of the suppression file in your own records, because many platforms won't carry suppressions over when you export and re-import.
  5. Verify the remaining list. This is the step most teams skip. Bounce logs only cover addresses you've already mailed, and verification covers everything else.
  6. Send only to Valid addresses, most engaged first. Hold Risky addresses (catch-all, disposable and role-based) until your main list has shown stable results.
  7. Measure the next send. Keep the total bounce rate under 2%. Google's sender guidelines advise keeping the spam rate below 0.1% and never letting it reach 0.3%. Spam complaints are a separate metric from bounces, but both reward clean, consented lists.

Bottom line: Stop, diagnose, fix your side, suppress, verify, then send carefully. Skipping step 5 leaves most of your list untested.

Which fix method works best at scale?

Each method covers a different slice of the problem. The table shows where each one stops working.

Method What it catches What it misses Limits or cost Best use
Suppress from bounce logs Addresses you've already mailed that failed Every address that died and was never mailed again Free Immediate first step
ESP auto-suppression Hard bounces the platform observes The rest of the list; suppressions often don't travel when you migrate Varies by platform; many label hard bounces as "cleaned" or add them to a bounce suppression list Ongoing safety net
Bulk verification with Unlimited Verifier Syntax, domain/MX, SMTP mailbox, catch-all domains, disposable and role-based addresses Engagement and consent Standard verification unlimited on every plan. Free: 150 emails per list, 25 lists a month. Pro: lists up to 25,000 emails, 25,000 deep verifications a month Cleaning the whole list before the next send
Real-time API check Each address at the point of entry Existing contacts already on the list API access on Pro, 100,000 emails a month Stopping new 5.1.1s from entering
Manual lookup One address at a time Scale Your time A handful of high-value contacts

What separates these options in practice:

When you compare vendors, check email verification pricing per address at your real volume, and read the criteria in our how to choose an email verifier guide. Our verifier roundup covers the tools themselves.

Bottom line: Suppress for speed, verify for coverage, and use the API to stop new failures at the door.

How do you clean 5.1.1 addresses with Unlimited Verifier?

Here is the workflow for a beginner. It works for any list you can export as a spreadsheet.

  1. Export your full contact list as a CSV. Include the email column and any engagement fields you have, such as last open date, last purchase or signup source. These help you segment later.
  2. Create a separate suppression file. Put every 5.1.1 address in its own CSV and label it with the campaign date. This becomes your permanent record.
  3. Sign up for a free account. The Free plan handles 25 lists a month of up to 150 emails each, which is enough to test the workflow on a sample.
  4. Upload your list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. If a list has more than 25,000 rows, split it before you upload, because Pro lists are capped at 25,000 emails each.
  5. Run the verification and read the three buckets.
    • Valid: safe for your next sends.
    • Invalid: remove and suppress permanently.
    • Risky: catch-all domains accept mail at the SMTP stage without confirming the mailbox, so they can't be verified. Disposable and role-based addresses like info@ also land here. The catch-all email verification page explains how these are handled.
  6. Export the results and save the counts. Export as CSV, Excel or JSON. Results are kept for 24 hours on Free and 30 days on Pro, so save your own copy.
  7. Re-import only Valid contacts into your ESP as a new segment, and add the Invalid ones plus your 5.1.1 suppression file to its suppression list. There are no native ESP, CRM or Zapier integrations, so this is an export-verify-import loop. If you'd rather automate it, you can call the email verification API from your own scripts.

Bottom line: Export, suppress the known failures, verify, keep Valid, and re-import with the suppressions attached.

What does a real clean cost? A 52,000-address worked example

This example is illustrative, and the verification percentages are hypothetical. The arithmetic and plan limits are real.

The problem. A B2B newsletter with 52,000 addresses sent one campaign and got 1,144 5.1.1 bounces:

1,144 ÷ 52,000 = 2.2% bounce rate

That is above the 2% ceiling, so the account needs attention. Sorting by domain showed 812 of the bounces (71%) across just nine domains, which pointed to acquired companies whose domains had been retired. The remaining 332 were scattered single-address failures.

Step 1: Suppress known failures.

52,000 − 1,144 = 50,856 addresses remain

Step 2: Check the plan fit. On the Free plan, 50,856 addresses at 150 per list needs:

50,856 ÷ 150 = 339.04, so 340 lists

That exceeds the Free plan's 25 lists a month, so Pro is the practical option. Pro has no list-count limit but caps each list at 25,000 emails, so the file splits into three parts: 25,000 + 25,000 + 856.

Step 3: Allocate deep verifications. Pro includes 25,000 deep verifications a month. Suppose 21,400 of the addresses came from the older imported segment, and you want those checked at the deep level:

21,400 deep checks, leaving 25,000 − 21,400 = 3,600 for spot-checks 50,856 − 21,400 = 29,456 addresses still get standard verification, which is unlimited on every plan

Step 4: Hypothetical results.

Bucket Count Share
Valid 43,610 about 86%
Risky 4,470 about 9%
Invalid 2,776 about 5%

Check: 43,610 + 4,470 + 2,776 = 50,856.

Step 5: Cost. One Pro month at $29 covers the whole clean:

$29 ÷ 50.856 (thousands of addresses) ≈ $0.57 per 1,000 addresses

The annual Pro plan works out to $25 a month billed annually, but for a one-time clean the monthly price is the honest comparison.

Step 6: Re-entry. Send to the 43,610 Valid addresses, most engaged first. Keep Risky addresses out until the main list shows stable bounce rates. Track the bounce rate on every send.

Bottom line: The clean costs under a dollar per thousand addresses and turns a vague "we had bounces" into a list you can show is clean.

How do you stop 5.1.1 bounces from coming back?

Most repeat spikes come from a few entry points, so prevention means checking data at each one.

Teams running email verification for ecommerce and SaaS programmes usually need both capture-time checks and a scheduled bulk pass, because the list keeps decaying between checks. Verification also supports email verification compliance and hygiene, but it can't prove a person opted in.

Bottom line: Check at capture, verify imports, keep suppressions through migrations, and re-verify on a schedule.

What mistakes keep 5.1.1 bounces coming back?

Bottom line: Most repeat 5.1.1 problems come from acting on the code without checking the pattern behind it.

How we compared (and limitations)

This guide is based on public documentation: the enhanced status code definitions in RFC 3463, the permanent-failure model in RFC 5321, Google's sender guidelines, and Amazon SES's documentation on bounce-rate thresholds. For industry practice on bounce handling and sender reputation, we also consulted public best-practice guidance from M3AAWG.

Some limits to keep in mind:

Bottom line: Use the codes and limits as a planning baseline, and check your own provider's wording and thresholds before you act.

Triage steps for a 550 5.1.1 bounce

  1. Suppress the address immediately. Do not retry.
  2. Read the provider text after the code to identify the rejecting server.
  3. Group bounces by domain. A cluster at one domain suggests a retired or acquired domain.
  4. If the bounced domain is yours, check MX records and recipient settings first.
  5. Check how the address entered your list (typo, old import, form abuse).
  6. Verify the unmailed remainder of the list and send only to Valid addresses.
  7. Keep total bounces well under 2% of sends.

Frequently asked questions

Should I retry a 550 5.1.1 bounce?

No. A 550 5.1.1 is a permanent hard bounce, meaning the mailbox is invalid at that server. Retrying will keep failing and can hurt sender reputation. Suppress the address after the first bounce and only re-add it if the person re-confirms consent through another channel.

What causes 550 5.1.1 errors?

The most common cause is that the mailbox was deleted, closed, or never existed. Other causes include typos in the address, retired or acquired domains, and misconfigured recipient settings on your own domain. The bounce text usually hints at which server rejected the message and why.

Is 550 5.1.1 the same as user unknown?

Usually yes. User unknown is a common wording of the 550 5.1.1 response, used by many servers. The exact phrase varies by provider, so the text after the code is the best clue to the specific reason for the rejection.

How is 550 5.1.1 different from 550 5.1.0?

Both are permanent recipient-related failures, but they describe different problems. 5.1.1 indicates a bad destination mailbox address, while the 5.1.0 family relates to sender address issues. Check the enhanced code and provider text to confirm which applies to your bounce.

Can a 550 5.1.1 address ever start working again?

Yes, occasionally, if someone re-creates the mailbox or a work address is reassigned. Treat the address as dead until the person re-confirms through a channel they have consented to. Do not automatically re-add it to sending lists.

Why do I see 550 5.1.1 for my own domain?

If bounces hit addresses on your own domain, check your MX records, catch-all settings, and recipient verification configuration. A misconfigured or changed mail host can make valid users appear unknown, so rule out your own setup before blaming the list.

How do I stop 550 5.1.1 bounces from happening again?

Verify addresses before sending, suppress hard bounces automatically, remove addresses that have not engaged in a long time, and capture addresses with double opt-in. Keeping total bounce rates low protects deliverability over time.

Does a 550 5.1.1 bounce affect my sender reputation?

It can. Hard bounces signal poor list quality to mailbox providers and to anyone monitoring your bounce rate. Repeated attempts to unknown addresses make this worse, so suppressing them quickly is one of the most effective protections you can apply.

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 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.