5.1.2: the recipient's domain does not exist in DNS

What the bounce means

The enhanced status code 5.1.2 means your mail server could not find the recipient's domain in DNS. It usually appears as 550 5.1.2 with text like “domain not found” or “host unknown,” though the reply code and wording vary; the enhanced code is the reliable part. Before any message can be delivered, the sending server looks up the domain half of the address for MX records (or, failing that, an address record) to learn where to connect. For a 5.1.2, that lookup came back empty: no MX, no fallback, nowhere to go.

That makes this bounce unusual. The message was never refused by a receiving server, because no receiving server exists for that name. Your authentication and reputation were never evaluated. The address is the problem, and there are only two ways it gets that way.

Typo or dead domain

• A typo in the domain half. The most common case: gamil.com, outlok.com, a missing letter in a company name. The local part may be perfect, but the domain it points at was never real.
• A genuinely dead domain. The domain existed when the address was captured and has since expired or been shut down. Corporate renames are a classic source: the company moved to a new name, ran the old domain for a transition period, and eventually let it drop. Every address on the old domain then returns 5.1.2 at once, which is why this code sometimes arrives in a cluster for one company.

How to check for yourself

You do not have to guess which case you are in: ask DNS directly. From any terminal, run dig MX theirdomain.com (or nslookup -type=mx theirdomain.com on Windows) and read the answer section. If there are no MX records, check whether the domain resolves at all with dig A theirdomain.com. Three outcomes matter:

• Nothing resolves. The domain is dead or misspelled. The bounce is correct and final; fix the address or suppress it.
• The domain resolves, but with no MX and no mail server on its A record. The domain exists but does not take mail. For sending purposes, treat it the same way: the address cannot receive.
• MX records exist and look healthy. Then the 5.1.2 was likely a transient DNS failure at send time (an expired-then-renewed domain, a registrar hiccup, a resolver problem on your side). A fresh send may go through.

How to handle it

• Verify, then suppress. Once you have confirmed the domain has no mail service, suppress every address on it rather than one at a time. Do not retry-loop a permanent code.
• Chase the obvious typos. If the domain is one letter off a major provider or a known customer, correct the record at the source instead of deleting the contact.
• Watch for renamed companies. A burst of 5.1.2 from one domain often means the organization moved. The people still exist; find the new domain and re-permission them there.

Frequently asked

What does a 5.1.2 bounce mean?

Your mail server tried to look up the domain half of the recipient address in DNS and found nothing to deliver to: no MX records and no fallback address record. The message never reached a receiving server, because DNS gave your server nowhere to connect. It is a permanent failure about the address, not about your sending setup.

How do I check whether the recipient domain really is dead?

Query DNS for the domain yourself with dig or nslookup: look up its MX records first, and if there are none, its A or AAAA records. If nothing resolves, the domain is dead or was typed wrong. If records do exist, the failure was likely a temporary DNS problem at send time and a later attempt may succeed.

Is 5.1.2 my fault as the sender?

No. The address is the problem: either its domain was typed wrong or the domain itself no longer exists. Nothing about your SPF, DKIM, DMARC, or reputation is involved, because no receiving server ever evaluated the message.

How is 5.1.2 different from 5.1.1?

5.1.2 fails on the domain half of the address: DNS has nowhere to send the message. 5.1.1 fails on the local part: the domain resolved, a real server answered, and it said no mailbox by that name exists.