The format of a null MX record
An ordinary MX record names a mail server and its preference, for example 10 mx1.example.com. (see what is an MX record). RFC 7505 defines a special form: preference 0 and a target of ., the DNS root, which is not a real host. In a zone file it looks like this:
static.example.com. 3600 IN MX 0 .
Two rules apply. The null MX must be the only MX record for that name; RFC 7505 says a domain publishing it must not advertise any other MX. And it applies to the exact name where it is published, so a subdomain with a null MX does not affect mail for the parent domain, and vice versa.
How senders treat a null MX
RFC 7505 is designed so that a null MX causes every delivery attempt to the domain to fail immediately. Because the domain does have an MX record, the sender does not fall back to its A or AAAA hosts, and since . is not a valid host name, there is nothing to connect to. Instead of queuing and retrying, the sender fails the message on the first attempt, and RFC 7505 defines a specific code for it:
556 5.1.10 Recipient address has null MX
That fast, permanent failure is the point. RFC 7505 notes that without it, mail to a domain with no listening server is typically retried for about a week before the sender gives up.
RFC 7505 also covers the sending side. A domain with a null MX cannot receive bounces or replies, so receiving servers may reject mail whose envelope sender uses that domain, with the code 550 5.7.27 (“Sender address has null MX”). For a domain that neither sends nor receives mail, RFC 7505 suggests pairing the null MX with an SPF record of v=spf1 -all, defined in RFC 7208, which states that no server is authorized to send for it.
Null MX vs. no MX record
These two situations look similar but behave differently.
- No MX record: Under RFC 5321 Section 5.1, if a domain has no MX records, senders treat its A or AAAA record as an “implicit MX” and try delivering to that host. Plenty of small domains receive mail this way, so a missing MX does not mean an address is undeliverable.
- Null MX: The domain owner has stated that no mail is accepted. Because an MX record exists, the implicit MX rule does not apply and there is no fallback to A or AAAA records.
- No MX and no A/AAAA: There is nowhere to deliver mail, so addresses at the domain are undeliverable.
A verifier that marks every domain without MX records as dead will wrongly reject real addresses, while one that ignores null MX will waste connection attempts and may misreport results.
Why it matters
- Cleaner bounces. Mail to a null MX domain fails at once with a clear reason, rather than lingering in a queue and arriving as a delayed bounce.
- List quality. Addresses at null MX domains can never receive mail. Sending to them adds hard bounces that count against your sender reputation.
- Less wasted effort. Senders stop retrying mail that can never be delivered, and domain owners make it clear that the domain is not a mail domain.
Where you will encounter null MX records
They are common on domains and subdomains that exist only for non-email purposes: static asset hosts, API endpoints, link shorteners, parked or defensively registered domains, and marketing microsites. A company might publish a null MX on app.example.com while example.com keeps its normal MX records.
How to check and handle it
- Check the domain’s MX records with
dig MX example.comor an online lookup. A single answer of0 .means null MX. - Remove addresses at null MX domains from your lists. They are permanently undeliverable.
- Fix your own domains. If you publish a null MX on a domain you send from, receivers may reject your mail. Use null MX only on domains that genuinely send and receive nothing, and add
v=spf1 -allto those. - Do not confuse it with a typo. An address at a null MX domain sometimes signals a mistyped domain, so check for a likely correction at signup.
Where RocketVerifier helps
RocketVerifier detects RFC 7505 null MX records and reports those addresses as undeliverable with a does_not_accept_mail sub_status. Domains that have no MX but do have an A or AAAA record are verified through the implicit MX instead of being rejected outright. You can inspect any domain’s mail records with the free MX lookup tool.