Topic · Email Infrastructure

Null MX record

A null MX record explicitly advertises that a domain does not accept email.

Email Security Glossary·Practical guidance
Share this definition LinkedIn X WhatsApp Email
01 / How it works

How it works

The DNS MX RR uses preference 0 with an exchange value of a single dot, per RFC 7505.

02 / What can go wrong

What can go wrong

Incorrectly configuring null MX on an active receiving domain will prevent legitimate inbound mail.

03 / What to check or do

What to check or do

Use null MX only for intentionally non-receiving domains and verify associated SPF and DMARC policies.

Practical scenario

Practical scenario

A brand has a defensive domain that will never receive mail. Leaving MX absent can still permit SMTP clients to attempt implicit delivery to the domain A record. An explicit null MX communicates the intended no-mail status.

Verification checklist

  1. Confirm the domain has no legitimate inbound recipients or forwarding needs.
  2. Publish an MX record with preference 0 and exchange a single dot (.)
  3. Verify the authoritative MX answer and ensure no competing ordinary MX records.
  4. Set a non-sending SPF policy and suitable DMARC protections for inactive domains.
Practical diagnosis

How to investigate Null MX record

Signal to investigate
A domain intended never to receive mail has no MX and accepts fallback delivery attempts to its A record.
Evidence to collect
Query MX and verify a single null MX with preference zero and target dot for a no-mail domain.
Common wrong conclusion
Null MX is not an email-sending prohibition; outbound identities need SPF/DMARC decisions too.

How to interpret the evidence

A no-mail domain without any MX can still invite SMTP clients to try an implicit exchange through an address record. A null MX explicitly says the domain accepts no inbound email. This is useful for defensive domains and hostnames that should never receive mail, but is inappropriate for domains with legitimate recipients or forwarding requirements.

What to change and how to verify it

First confirm that no business process expects inbound mail. Publish the standards-defined null MX, verify the exact record at authoritative DNS and check that no competing ordinary MX remains. Review outbound spoofing controls separately because null MX does not address all sender-identity abuse.

Illustrative diagnostic — substitute your authorized domain or host
dig +short MX example.com
Educational example; not validated against your live infrastructure.
NEXT STEP

Put this into practice

Run a focused check, then explore protection if your domain needs it.

Authoritative reference ↗