550 5.4.310 DNS domain does not exist

A Microsoft 365 user tried to send to a domain and Exchange Online could not find it in DNS: no MX record, no A record, nothing. This is a bounce for mail leaving Microsoft, and it means the recipient domain is misspelled, expired or has never had mail set up.

What the server replies

550 5.4.310 DNS domain example.invalid does not exist [Message=InfoDomainNonexistent] [LastAttemptedServerName=example.invalid] [LastAttemptedIP=] [AM0PR06MB1234.eurprd06.prod.outlook.com]

Sent by
Microsoft 365
Type
PermanentRetry fails
About
Recipient problems
Enhanced code
5.4.310

Who sends it

Exchange Online transport when it tries to route an outbound message and the DNS lookup for the recipient domain returns NXDOMAIN. Sender is a Microsoft 365 mailbox; the NDR comes from the tenant's own servers.

Why it happens

  • A typo in the recipient domain (gmial.com, outlok.com).
  • The recipient's domain registration lapsed and its DNS zone disappeared.
  • The domain exists but has no MX and no A record, so there is nowhere to deliver.
  • The domain is brand new and its nameservers have not propagated yet.

How to fix it

  1. Check the spelling

    Most of these are typos. Compare the domain against a known-good message from the recipient.

  2. Look the domain up

    Run the domain through an email DNS checker. If there are no MX and no A records, the recipient has to fix their DNS; nothing on the sending side will deliver it.

  3. Retry once for a new domain

    If the domain was registered today, DNS can take an hour or two to appear at Microsoft's resolvers. Resend later.

Check it yourself

These free tools show the records and connections behind this code for your own domain or server.

Related codes

Sources

Fewer bounces to look up.

Faivelo sends from authenticated, warmed infrastructure, turns permanent bounces into one clean event for your application and keeps the address out of future sends.

Send with Faivelo

Free tier included. No card needed.