How to fix: MX Record Missing
No MX record exists for this domain. Domains that send or receive email must have an MX record. Without it, mail delivery to this domain fails and email spoofing countermeasures (SPF/DMARC) lack a target.
Why it matters
Without MX records, inbound mail to this domain bounces. If the domain is used to send mail without an MX record, receiving servers may treat it as a red flag and mark mail as spam.
MX records direct incoming mail to the correct mail server. Their absence means the domain cannot receive email. DMARC and SPF records also become less meaningful without a functioning mail infrastructure.
How to fix it
- 1Publish an MX record pointing to your mail server with the appropriate priority.
- 2Verify with: dig +short MX example.com
Code examples
DNS zone file
example.com. IN MX 10 mail.example.com.
example.com. IN MX 20 mail-backup.example.com.Verify MX
dig +short MX example.comReferences
Detected automatically by VulnRadar. The check id is dns-mx-record-missing, stable across every scan so you can filter or diff on it.
More dns checks
Questions
- How severe is MX Record Missing?
- VulnRadar rates this medium 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-mx-record-missing, 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.