5.4.4 means the sending server could not work out where to deliver — the recipient’s domain has no usable MX or address in DNS.
| Code | 5.4.4 |
| Meaning | Unable to route |
| Kind | Permanent failure — the sender gives up |
| Sent in reply to | In the sender’s own bounce |
| What the sender does | Returns the message to the sender |
| Defined in | RFC 3463 |
Paste your bounce
Paste the line with the code — or the whole bounce: we explain each code in it, say whether the sender will try again, and link the service’s own page where it has one. It is read in your browser; nothing is sent.
What causes it
- The recipient’s domain does not exist, or has no MX or A record.
- The sending server’s own DNS settings are wrong.
What to do
- Check the recipient’s domain — its MX records.
- At Exchange Server: check the DNS settings of the transport service and the network adapter.
What each provider means by it
| Who | What they say |
|---|---|
| Exchange Server | 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain. |
| Gmail | Reports a recipient domain it cannot find as 553 5.1.2. |
Sources
Checked on 27 September 2026 against these official sources:
- Simple Mail Transfer Protocol (SMTP) Enhanced Status Codes Registry — iana.org
- DSNs and NDRs in Exchange Server — learn.microsoft.com
- Gmail SMTP errors and codes — knowledge.workspace.google.com