What is a dead domain?

A dead domain is a domain that no longer hosts a working mail server. The domain might still be registered. The website might even load a parked page. But if you send mail to anything@that-domain.com, the message has nowhere to land because there is no mail server accepting connections on port 25.

There are a few flavors of dead, and they fail in slightly different ways:

• No MX record and no A record fallback. The domain's DNS has no Mail Exchange (MX) record pointing at a mail server, and no A record to fall back on. Sending servers get a permanent lookup failure. Bounce code: 550 5.1.2 or 550 Host unknown.
• MX record points at a host that no longer exists. The MX is there, but the hostname it points to does not resolve. Same outcome, slightly different bounce text.
• MX resolves but nothing answers on port 25. The mail server hardware is gone, the cloud instance was terminated, or the company shut down. Connections time out or get refused. You see 421 temporary failures that eventually convert to permanent ones after retry windows expire.
• Domain expired entirely. Whois shows the registration lapsed. DNS still caches for a while, then everything goes dark. These often get re-registered by squatters, which is when dead domains become trap domains - a separate and worse problem.

All of these produce hard bounces, which is the SMTP server's way of saying "do not try again, ever." The SMTP standard (RFC 5321) defines any 5xx reply as permanent. Mailbox providers like Gmail treat repeat hard bounces as a strong signal that you are not maintaining your list.

How dead domains end up on your list

They accumulate quietly. The address was valid when someone typed it in. Then the company folded, the side project got abandoned, the domain owner stopped paying the registrar, or the small business migrated to a new domain and let the old one expire. None of that triggers a notification to you. The address just stops working, and you keep mailing it for months or years until you look at your bounce logs.

B2B lists rot the fastest because small businesses fold all the time. Consumer lists rot through personal domain churn, which is rarer but still happens. Lists you bought, scraped, or got through B2B lead databases start out with a much higher dead-domain rate than organic signups, because nobody is maintaining them on your behalf.

How to detect them before sending

Three checks, cheapest to most expensive:

1. DNS lookup. Query the domain for MX, then A records. If both are missing, the domain is dead at the DNS layer. This is free and fast.
2. SMTP handshake. Open a connection on port 25 to the resolved MX host, say HELO, and see if the server responds. If it refuses, times out, or returns 5xx on RCPT TO, the mailbox is unreachable.
3. Full validation. A service does both of the above plus catches catch-all configurations, spam traps, and role accounts. RME's list cleaning service is one example, but the technique is standard across the industry.

If you do not want to validate, the cheap proxy is to watch your bounces. Most ESPs surface hard-bounce reasons in their dashboards. Anything tagged "host unknown," "no MX record," "domain not found," or 5.1.2 is a dead domain.

Why you cannot just ignore them

Every message you send to a dead domain is a hard bounce. Once your hard-bounce rate climbs above roughly 2% of sent volume on any single send, mailbox providers start throttling you. Hit 5% and you are in reputation damage territory, which affects deliverability for every other address on your list, not just the dead ones.

This is why list hygiene matters for sender reputation: a handful of dead domains in a 50k list will not move the needle, but 3,000 of them in a 50k list will get you rate-limited at Gmail by Tuesday.

Remove dead domains on detection. Do not retry them. Do not put them in a "maybe try again next quarter" segment. They are not coming back.