What is “MX lookup failed”?

You send an email, and instead of a delivery confirmation, you get back an error that says something like "MX lookup failed" or "host not found" or a 5.4.4 status code. What just happened?

An MX record (Mail Exchange record) is a DNS entry that tells the internet where to deliver email for a domain. When your sending server tries to deliver a message to captain@deepcurrent.io, the first thing it does is look up the MX records for deepcurrent.io to find out which mail server should receive it. If that lookup fails, delivery stops immediately. The server has nowhere to send the mail.

"MX lookup failed" is almost always a hard bounce. The most common reasons it happens are worth knowing, because they point to very different fixes.

• No MX records configured. The domain exists, but whoever set it up never added email routing. This happens with new domains, or domains used purely for web traffic with no email intended.
• The domain has expired. When a domain registration lapses, the DNS records disappear with it. Any email sent to that domain will fail immediately.
• A typo in the address. If you're attempting to email someone at @deepcurrnt.io instead of @deepcurrent.io, the MX lookup will fail because that domain doesn't exist at all.
• Recent DNS changes not yet propagated. DNS changes can take up to 48 hours to spread across the internet. A temporary lookup failure during this window might resolve on its own.
• A DNS server outage on the recipient's side. Less common, but it does happen. This usually shows up as a temporary failure rather than a permanent one.

The distinction between temporary and permanent matters a lot here. A 5.4.4 code (or "unable to route" error) with a consistent MX lookup failure is a hard bounce. You should suppress that address immediately and not retry it. If it's a DNS propagation issue or a brief server timeout, your ESP may retry automatically before marking it as a failure.

To check manually, you can run nslookup -type=MX domain.com or dig MX domain.com in your terminal. If you get no results back, the domain genuinely has no MX records. If you get a timeout, it's more likely a temporary DNS issue.

From a list hygiene standpoint, MX lookup failures that show up as hard bounces are a signal that these addresses should come off your list. Repeatedly sending to domains with no MX records will hurt your sender reputation over time. If you're seeing a lot of these from the same campaign, it's worth checking whether your list is old or sourced somewhere questionable.

If you're not sure whether your bounces are hard or soft, or you want to clean out addresses that are likely to fail before you send, we can help with that. RME Clean validates addresses before they hit your sending queue, so you're not burning reputation on domains that can't receive mail.