Skip to main content
InfoDNS

How to fix: Null MX Recommended for Non-Mail Domain

This domain has no MX record and no SPF record either, consistent with a domain that does not send or receive email. RFC 7505 defines a null MX record as the explicit way to declare that intent in DNS, rather than leaving mail-related records simply absent.

Why it matters

This is a hygiene recommendation, not a vulnerability: leaving mail intent unstated doesn't expose anything on its own, but some receiving mail servers and anti-spoofing tooling treat a domain with no MX and no null MX as ambiguous rather than confirmed non-mail, which can affect how mail claiming to be from this domain is scored.

RFC 7505 defines a single MX record with exchange '.' (priority is ignored) as the standard way for a domain to declare it accepts no mail. Without it, an absent MX record is just silence, indistinguishable from a domain that intends to send or receive mail but has a misconfiguration. Publishing a null MX, together with a hard-fail SPF record, is the documented way to close that gap for a domain that genuinely never sends or receives mail.

How to fix it

  1. 1Add a null MX record: yourdomain.com. IN MX 0 .
  2. 2Pair it with a hard-fail SPF record: v=spf1 -all
  3. 3Skip this if the domain does send or receive mail through infrastructure this scan couldn't see, for example mail routed only through a parent or organizational domain.

Code examples

DNS zone file

DNS
example.com. IN MX 0 .
example.com. IN TXT "v=spf1 -all"

References

Detected automatically by VulnRadar. The check id is dns-null-mx-recommended, stable across every scan so you can filter or diff on it.

See every dns check

Questions

How severe is Null MX Recommended for Non-Mail Domain?
VulnRadar rates this info severity in the dns category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id dns-null-mx-recommended, which stays the same between runs so you can filter, diff, or gate CI on it.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for null mx recommended for non-mail domain

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

Null MX Recommended for Non-Mail Domain fix | VulnRadar