A null MX — one MX record with preference 0 and the host “.” — says a domain accepts no email at all (RFC 7505). Senders fail at once instead of trying the domain’s web server for days; without any MX, mail is sent to the domain’s A or AAAA address instead.
| What it is | No mail at all |
| The record | 0 . — a single record, preference 0, host “.” |
Does a domain take mail?
Enter a domain: we read its MX records, say whether it publishes a null MX and what else is there — and, without one, where senders would deliver instead.
The record
One MX record, and no other: preference 0, and a single dot for the host.
example.com. MX 0 .
And, so that no one can send mail as the domain either:
example.com. TXT "v=spf1 -all"
_dmarc.example.com. TXT "v=DMARC1; p=reject"
Worth knowing
It must be the only MX. A server refusing a recipient because of it should answer 556 5.1.10; one refusing a sender whose domain has it, 550 5.7.27. Postfix and Exim both honour it; how Gmail and Microsoft treat it is not documented — and Gmail uses 5.7.27 for something else.
Do not send mail from a domain with a null MX: receivers may refuse it. Pair it with an SPF record of v=spf1 -all and a DMARC policy of reject.
Questions
What is the difference between a null MX and no MX?
With no MX, mail is sent to the domain’s own A or AAAA address — usually a web server that should not receive it, so senders retry for days. A null MX says there is nowhere to send, so they give up at once.
Sources
Checked on 27 September 2026 against these official sources:
- RFC 7505: A “Null MX” No Service Resource Record for Domains That Accept No Mail — rfc-editor.org
- RFC 5321: Simple Mail Transfer Protocol — rfc-editor.org
- Postfix Configuration Parameters — postfix.org
- 17. The dnslookup router — exim.org