SMTP: 550 5.1.2 Domain not found / 554 5.4.4 Unable to resolve MX / Host or domain name not found
Mail cannot be routed because the recipient domain has no MX (or A) record, or DNS for it fails.
550 5.1.2 Domain not foundDomain not found MXUnable to resolve MXHost or domain name not found. Name service error for name=example.com type=MX554 5.4.4 Unable to route Meaning
When delivering, an MTA queries the MX records of the domain; if none exist it falls back to the A record, and fails if that is missing too. Typos in the domain, expired domains, deleted DNS zones, or MX entries pointing at a CNAME (not allowed) are common.
Common causes
- Typo in the recipient domain
- Domain expired or DNS zone removed
- No MX record published for the domain
- MX points to a CNAME or to a host with no A record
- Temporary DNS outage (shows as 4xx)
⚡ Quick fix
- Check the domain spelling
dig MX domain.comshould return one or more hosts- Fix MX to point to hostnames with A/AAAA records (not CNAME or IP)
Detailed fix by platform
Linux
dig +short MX example.comand thendig +short A mail.example.comfor each MX host
How to diagnose
- MX — Records returned?
- Hosts — MX targets resolve?
- Domain — Registered and active?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 421 4.7.0 Try again later (rate limited) SMTP: 421 4.7.0 Our system has detected an unusual rate of unsolicited mail originating from your IP address. Mail sent from your IP address has been temporarily rate limited
- 450 4.7.1 Greylisted, please try again later SMTP: 450 4.7.1 <user@example.com>: Recipient address rejected: Greylisted, see http://postgrey.schweikert.ch/help/example.com.html
- 550 5.1.1 550 5.1.1 The email account that you tried to reach does not exist (User unknown)
Most viewed in Email / SMTP
- 550 5.7.1 550 5.7.1 Relaying denied / Message rejected as spam / Unauthenticated email not accepted
- 550 5.7.26 550 5.7.26 This mail has been blocked because the sender is unauthenticated (SPF/DKIM/DMARC)
- SES: Maximum sending rate exceeded Amazon SES: Throttling — Maximum sending rate exceeded (454 Throttling failure)
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 4 Nov 2026