← Back to Learning Hub

DNS Records • Intermediate • 6 min read

Null MX Record (RFC 7505): Domains That Accept No Mail

How a single null MX record tells senders a domain receives no email, why it beats an empty SPF alone, and how it cuts backscatter and bounce delays fast.

A null MX record is a single line of DNS that tells every sending mail server a domain receives no email, so they stop trying immediately and bounce the message fast. It is defined in RFC 7505 (current as of November 2026) and looks like example.com. IN MX 0 ., a priority of 0 pointing at the root label, a dot, which is a deliberately unusable target. This guide explains what the null MX does, why it is better than having no MX record or an SPF record alone, and how to publish it correctly on a parked or send-only domain.

What a null MX record is

The entire mechanism is one special MX record. The target is a single dot, which represents the DNS root and can never be a real mail host. By convention and by RFC 7505, a domain that publishes exactly one MX record with preference 0 and a target of "." is declaring, explicitly and machine-readably, that it does not accept mail. A sender that sees it knows there is no point attempting delivery and can reject or bounce the message right away.

example.com.  IN MX 0 .

Two rules make it valid: the preference must be 0, and it must be the only MX record for the name. Mixing a null MX with real MX records is undefined and defeats the purpose.

Why "no MX record" is not good enough

You might think a domain with no MX record already refuses mail, but the rules say otherwise. When a domain has no MX record at all, senders are required to fall back to the domain's A or AAAA record and attempt delivery to that address, a behavior called the implicit MX rule. So a parked domain that happens to have a web server will still receive connection attempts on port 25, generate slow timeouts, and leave senders guessing. The null MX removes that ambiguity: it is a positive statement of "no mail here" rather than the absence of a statement, and it short-circuits the A-record fallback entirely.

Null MX versus an SPF record alone

People often reach for an SPF record of v=spf1 -all to lock down a non-sending domain, and that is correct, but it solves a different problem. SPF governs sending: it tells receivers which servers may send mail as your domain, and -all says none. The null MX governs receiving: it tells senders you accept no inbound mail. They are complementary, not interchangeable.

ControlDirectionWhat it says
Null MX (MX 0 .)InboundThis domain accepts no email; do not attempt delivery
SPF v=spf1 -allOutboundNo server is authorized to send mail as this domain
DMARC p=rejectOutboundReject mail failing authentication; strengthens the SPF stance

A fully hardened non-mail domain publishes all three: a null MX so nobody tries to deliver to it, and an SPF plus DMARC pair so nobody can convincingly spoof mail from it.

The real benefits

  • Faster bounces: a sender that mistypes an address to your parked domain gets an immediate rejection instead of waiting out delivery retries for hours or days.
  • Less backscatter: because legitimate senders are told up front there is no mailbox, there is less misdirected mail and fewer delayed bounce storms.
  • Clear intent: security scanners and mail systems can see the domain is deliberately mail-free, which reduces the chance it is abused as a fake sender or target.
  • No stray listeners: the A-record fallback is cut off, so a web-only host does not quietly field SMTP connections it was never meant to answer.

Publishing a null MX step by step

  1. Confirm the domain really sends and receives no mail. If anything, even a single alias or forwarder, relies on inbound mail, do not do this.
  2. Remove every existing MX record for the name.
  3. Add exactly one MX record: preference 0, target "." (a lone dot, which most control panels accept literally).
  4. Add v=spf1 -all as a TXT record to close off outbound spoofing.
  5. Optionally add a DMARC record with p=reject for the strongest anti-spoofing posture.
  6. Verify with a lookup that the null MX is the only MX present.

Reading and verifying it

A correct null MX shows up in a lookup as a single MX line with priority 0 and a bare dot as the target:

$ dig MX example.com +short
0 .

If you see any other MX host alongside it, or the record is missing, the declaration is not valid. A well-behaved sending server that encounters the null MX will log an immediate rejection such as "domain does not accept mail" rather than a timeout, which is exactly the fast failure you want.

When to use it, and when not to

Null MX is ideal for parked domains, brand-protection registrations you never read mail on, and send-only domains such as a transactional-mail subdomain that pushes notifications out but should never receive replies. It is the wrong choice the instant any real mailbox, alias, catch-all, or forwarder depends on inbound delivery, because you would be telling the world to refuse mail you actually want. When in doubt, check what currently points at the domain before you publish.

For the mechanics of ordinary inbound routing that the null MX overrides, see our guide on MX record priority and backup MX, and to get the outbound half of the lockdown right, read SPF all mechanisms on what softfail, hardfail, and neutral really mean.

After publishing, run the domain through the Valla DNS domain health check to confirm the null MX is the only MX record and that your SPF and DMARC posture lines up with a true no-mail domain.

What exactly does a null MX record look like?

It is a single MX record with preference 0 and a target of a lone dot, written as MX 0 . for the domain. It must be the only MX record on the name; combining it with a real mail host makes the declaration invalid.

Is a null MX better than having no MX record at all?

Yes. With no MX record, senders fall back to your A or AAAA record and attempt delivery there. A null MX cuts off that implicit fallback and states plainly that the domain accepts no mail, producing an immediate rejection instead of a slow timeout.

Do I still need an SPF record if I publish a null MX?

Yes, because they cover opposite directions. The null MX stops inbound delivery attempts, while SPF with v=spf1 -all stops anyone from sending mail as your domain. A non-mail domain should publish both, ideally with DMARC p=reject as well.

Will a null MX break anything on a domain that sends email?

It only affects inbound mail, so a strictly send-only domain is fine. But if any alias, forwarder, or mailbox relies on receiving mail, a null MX will cause legitimate messages to bounce, so verify there is no inbound dependency first.

How do senders react when they see a null MX?

A compliant sending server treats it as a permanent "no mailbox" signal and rejects or bounces the message immediately rather than retrying. This reduces delivery delays, backscatter, and misdirected mail aimed at the domain.

Troubleshooting box

If results look inconsistent, compare authoritative nameservers first, then recursive resolvers by region. Capture snapshots every 10 minutes for deterministic incident timelines.

Try VallaDNS free →

Intermediate • 6 min

How to Find a DNS Record's TTL (Current Value)

Find the TTL currently set on a DNS record: read the TTL column in dig and nslookup, tell the authoritative TTL from a resolver's countdown, and confirm a change.

Intermediate • 7 min

How to Check If Nameservers Have Propagated

Nameserver changes live at the parent TLD and follow the registry NS TTL, not your zone. Check the parent delegation and confirm the new NS set worldwide.