SMTP error code

550 5.1.10: recipient not found in Microsoft 365

550 5.1.10 means Microsoft 365 couldn't find the recipient. Usually the address is wrong or the mailbox is gone, which makes it a hard bounce. Two less obvious causes: a forwarding rule that points to a dead address, and bounces for mail you never sent.

Updated October 9, 2026 · 4 min read

Reply code
550 (RFC 5321)
Enhanced code
5.1.10 (registry: Recipient address has null MX)
Sent by
Microsoft 365 / Exchange Online
Bounce type
Hard bounce

Verification would have caught it

When the address you wrote to doesn't exist, a verification gets the same “not found” from Microsoft 365 and reports it as undeliverable. It can't help with backscatter or a recipient's broken forwarding rule.

550 5.1.10 Recipient not found in Microsoft 365, and the three causes Microsoft lists

What 550 5.1.10 means

550 5.1.10 is how Microsoft 365 reports that the recipient doesn’t exist. Microsoft’s NDR reference lists it as Recipient not found, and its article on 550 5.1.10 says the recipient’s address doesn’t exist or couldn’t be found.

The code itself means something else in the standard. The IANA registry assigns X.1.10 to “Recipient address has null MX” (RFC 7505), with the basic code 556, for domains that declare they accept no mail at all. Microsoft uses it for an ordinary unknown mailbox.

Microsoft 365 has three ways of saying “no such recipient”:

ReplyWhen you see it
550 5.1.10 Recipient not foundThe address isn’t known in the recipient’s Microsoft 365 organization
550 5.1.1 Bad destination mailbox addressAlso an unknown address; see 550 5.1.1
550 5.4.1 Recipient address rejected: Access deniedRejected at the edge by Directory-Based Edge Blocking; see 550 5.4.1

For Hotmail and Outlook.com addresses, Microsoft’s NDR reference lists a different text for a recipient that can’t be found: 550 5.5.0 Requested action not taken: mailbox unavailable.

Three reasons Microsoft lists

  1. The address doesn’t exist. A typo, an old address, or a mailbox deleted when someone left. Outlook’s Auto-Complete list can keep suggesting an outdated entry long after the address stopped working.
  2. The recipient forwards to a dead address. Your message reached a real mailbox, whose inbox rule or forwarding setting passed it to an address that doesn’t exist. The address in the bounce then differs from the one you wrote to.
  3. Backscatter. You never sent the message. A spammer put your address in the From field, wrote to a non-existent recipient, and the bounce came to you. Microsoft calls backscatter harmless and the resulting NDRs useless. If you get many, it suggests an anti-malware scan of your device and asking your admin to set up SPF; the SPF record generator writes the record.

How to fix 550 5.1.10 as the sender

  1. Compare the addresses. Open the bounce and your copy in Sent Items. Same address: it’s wrong or gone. Different address: the recipient forwards to a broken one, and only they can fix that.
  2. Remove the stale Auto-Complete entry. In Outlook, delete the suggestion, type the full address by hand and send again.
  3. Ask for the current address through another channel if you’re unsure, and remove the old one from your contacts and mailing lists so it doesn’t keep bouncing.
  4. Ignore true backscatter. No action is needed for bounces of messages you didn’t send.

If you run the Microsoft 365 tenant

Microsoft’s article gives these admin checks:

  1. Does the recipient exist? In the Microsoft 365 admin center, search Users > Active users and check that the user name matches the address senders use. If it doesn’t exist, create a mailbox or a contact. A mailbox in Exchange Online also needs a license.
  2. Broken forwarding. Turn off email forwarding on the user, and check Mail flow > Rules in the Exchange admin center for redirect rules that point to bad addresses.
  3. Accepted domain type. Use Internal Relay only if your hybrid setup routes mail to on-premises servers through a matching connector; otherwise the change can break mail flow.
  4. Hybrid directory sync. If the user was just created on-premises, force a delta sync on the Microsoft Entra Connect server and check again:
Start-ADSyncSyncCycle -PolicyType Delta
  1. MX record. Run Check DNS for the domain under Settings > Domains. Keep a single MX record pointing to Microsoft 365; DNS changes can take up to 72 hours to spread.

Would email verification have prevented it?

For the main cause, yes. An email verification asks Microsoft 365 about the recipient before any message is sent; an address that would bounce with 550 5.1.10 comes back as undeliverable. Check one address with the email checker or a whole list with the bulk email verifier, and remove the dead ones before the next send. The guide to Delivery Status Notification (Failure) shows how such bounces look when they do reach you.

Verification can’t help with the other two causes. A recipient’s broken forwarding rule sits behind a valid address, and backscatter comes from messages you never sent.

Stop bounces before they happen

Most hard bounces come from addresses that don't exist. An email verification asks the receiving server about the mailbox without sending anything, so you can remove bad addresses before your next send.

Frequently asked questions

What does 550 5.1.10 mean?

Microsoft 365 couldn't find the recipient's address in the organization you wrote to. Microsoft's description is “Recipient not found”. Most often the address has a typo or the mailbox was deleted.

What is the difference between 550 5.1.1 and 550 5.1.10?

For you as a sender, very little: both say the mailbox doesn't exist, and both are hard bounces. Microsoft lists 5.1.1 as “Bad destination mailbox address” and 5.1.10 as “Recipient not found”. In the official registry, X.1.10 actually means a domain that publishes a null MX, which is not how Microsoft uses it.

Why did I get a 550 5.1.10 for an email I didn't send?

A spammer probably forged your address as the sender of a message to a non-existent recipient, and the bounce came back to you. Microsoft calls this backscatter. It doesn't mean your account was hacked; your admin can reduce it by publishing SPF for your domain.

How do I fix 550 5.1.10 in Outlook?

Delete the recipient's entry from Outlook's Auto-Complete list, type the full address again and resend. If the address in the bounce differs from the one in your Sent Items, the recipient has a forwarding rule to a broken address and needs to fix it.

Related codes and guides

Email validation API

Validate emails in your app

emailvalidation.io checks syntax, MX records and the mailbox over SMTP, flags disposable, role and free addresses and returns a quality score, in one request.

/v1/info Email validation API Read the documentation

100 free validations every month. No credit card required.

GET https://api.emailvalidation.io/v1/info?email=support@emailvalidation.io

{
  "email": "support@emailvalidation.io",
  "user": "support",
  "tag": "",
  "domain": "emailvalidation.io",
  "format_valid": true,
  "mx_found": true,
  "smtp_check": true,
  "catch_all": null,
  "role": true,
  "disposable": false,
  "free": false,
  "score": 0.64,
  "state": "deliverable",
  "reason": "valid_mailbox",
  "did_you_mean": ""
}

Start using our email validation software today!

Get 100 validations per month for free