5.4.4

Enhanced Status Code 5.4.4: Unable to Route

Permanent failure High severity Network RFC 3463
What it means

Enhanced Status Code 5.4.4 means “Unable to Route.” The mail system could not work out where to send the message next. Almost always a DNS problem: the recipient domain has no usable MX record, or the records point somewhere unreachable.

At a glance
Code5.4.4
Bounce typeHard (permanent)
SeverityHigh
CategoryNetwork
What to doSuppress the address; do not retry
StandardRFC 3463
What it looks like in your mail logs 
550 5.4.4 Unable to route: no MX, A or AAAA record found for the recipient domain

What does 5.4.4 mean?

Enhanced status code 5.4.4 means unable to route. RFC 3463 defines it as the mail system being unable to determine the next hop for the message. As a permanent code it says the routing question has a definite answer and the answer is that there is nowhere to send this.

The recipient domain having no MX record is the usual cause. Where no MX exists, SMTP falls back to the A or AAAA record for the domain, so a domain with neither has no route at all. A domain that has expired, that was mistyped, or that never hosted mail all produce the same result. A null MX record, a single dot, is the explicit way for a domain to declare it accepts no mail, and RFC 7505 assigns that its own code in 5.1.10.

The less obvious cause is local: a mail server with a misconfigured relay or transport map may be unable to route mail it should handle perfectly well. If 5.4.4 appears for destinations you know are valid, look at your own routing tables before blaming their DNS, particularly on servers with split delivery or conditional forwarding.

How 5.4.4 plays out

Your server attempts delivery
The recipient server returns a permanent 5.4.4 rejection
This is a hard bounce: the message will not be accepted as sent
Suppress the address and fix the root cause before resending

Where 5.4.4 sits: soft vs hard bounce

Soft bounce (4xx) Hard bounce (5xx)
NatureTemporaryPermanent
SMTP class4xx5xx
What to doLet it retrySuppress the address
Recoverable?OftenNo
5.4.4 is✓ this code

Common causes of 5.4.4

  • The recipient domain publishes no MX, A or AAAA record
  • The domain name is mistyped, so it does not exist
  • The domain has expired and its DNS no longer resolves
  • MX records exist but point at hostnames that do not resolve
  • A local relay or transport map is misconfigured and cannot route the destination
  • A smarthost is defined for a domain but is itself unresolvable

How to fix 5.4.4

  • Look up the MX records for the recipient domain and confirm they resolve to addresses
  • Check the domain spelling against the recipient address, since typos are the most common cause
  • Confirm the domain has not expired
  • If MX hostnames exist but do not resolve, the recipient domain has a DNS fault to fix
  • Inspect your own transport maps and relay configuration for destinations you know are valid
  • Check 5.1.10 if the domain publishes a null MX, which is a deliberate refusal rather than a fault

Frequently asked questions

What does SMTP error 5.4.4 mean?
It means your mail system could not determine where to send the message next. In practice the recipient domain has no usable MX record, and no A or AAAA record to fall back on, so there is no server to deliver to. It is permanent, so retrying will not help.
How do I check whether a domain can receive mail?
Look up its MX records, and if there are none, look up A and AAAA, because SMTP falls back to those. If all three are absent the domain cannot receive mail at all. If MX records exist, confirm the hostnames they name actually resolve to addresses, since an MX pointing at a dead hostname routes nowhere.
Could this be my server rather than their domain?
Yes, and it is worth checking when the destination is one you know works. A misconfigured transport map, a relay rule, or a smarthost that no longer resolves will produce 5.4.4 for domains whose DNS is perfectly healthy. If other senders can reach the domain and you cannot, the fault is local.
What is a null MX?
A single dot as the MX target, which is the explicit way for a domain to declare it accepts no mail at all. RFC 7505 defines it, and it is a deliberate configuration rather than a mistake, commonly used on domains that only serve a website. A recipient at such a domain has its own code, 5.1.10.
Should I suppress addresses that return 5.4.4?
Yes, after confirming the domain is genuinely unroutable rather than the fault being local. A domain with no mail route will not accept mail from anyone, so continuing to try wastes queue capacity and contributes to a bounce rate that receivers hold against you.

Related bounce codes

5.1.2 Bad Destination System Address - Domain Not Found 5.1.10 Recipient Address Has Null MX 4.4.0 Other Network or Routing Status 5.4.1 Relay Access Denied 5.4.6 Routing Loop Detected

Sources & further reading

RFC 3463 · The standard that defines this reply code IANA registry · The authoritative list of enhanced status codes and their meanings
Reviewed by Jennifer Jackson, Email Deliverability Analyst · June 2026 ← All bounce codes