Skip to content
AdminKit

Null MX record

What is Null MX record?

A null MX record, standardized in RFC 7505, is a single MX record pointing to the root domain that tells senders a domain explicitly accepts no email at all, instead of leaving mail handling undefined. AdminKit's MX lookup tool reports a null MX explicitly, rather than as a missing or broken record.

By AdminKit team, Netbase JSC · Updated

A null MX record is a specific MX record — a single record pointing to the root domain (”.”) — that a domain publishes to explicitly declare it doesn’t accept email at all, standardized in RFC 7505 (a Proposed Standard per its IETF Datatracker entry). Before null MX existed, a domain that sent no mail had no standard way to say so: it would either publish no MX record, which falls back to trying the domain’s own A/AAAA record for SMTP delivery under RFC 5321’s implicit MX rule, or leave mail handling undefined, leaving senders unable to tell a missing server from a misconfiguration. Publishing a null MX tells sending servers to reject outgoing mail to that domain immediately, useful for domains used only for hosting or infrastructure, where no one should ever email that name — the opposite of a catch-all address, which accepts mail for any local part at a domain rather than refusing all of it. M3AAWG’s Protecting Parked Domains Best Common Practices recommends exactly this: publishing a null MX record to signal that a parked domain accepts no mail, closing off a path abusers otherwise exploit. The UK government’s guidance to protect domains that don’t send email lists a null MX record (priority 0, value ”.”) alongside SPF, DMARC and empty DKIM records, while noting that some DNS providers do not support creating one. A sender that still attempts delivery typically gets back a rejection the originating server renders as a delivery status notification rather than a silent failure. AdminKit’s MX lookup tool reports a null MX explicitly, rather than showing it as a missing or broken record.

AdminKit groups null MX record under its email authentication cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

What does a null MX record tell a sending server?

To reject outgoing mail to that domain immediately, since the domain has explicitly declared it accepts no email at all.

How did domains signal they accept no mail before null MX existed?

They had no standard way to -- publishing no MX record falls back to trying the domain's own A/AAAA record under RFC 5321's implicit MX rule, leaving senders unable to tell a missing server from a misconfiguration.

What does a null MX record actually look like?

A single MX record pointing to the root domain (".").

Which RFC standardizes the null MX record?

RFC 7505.