How to fix: No Backup MX Server
Only a single MX server exists with no higher-priority fallback. If the primary MX goes down, inbound mail is lost or deferred until the server recovers.
Why it matters
During primary MX outages, inbound mail queues at the sender for minutes or hours. If the outage is long enough, senders give up and mail is permanently lost.
Multiple MX records with different priorities provide redundancy. When the primary MX (lowest number) is unreachable, senders try the next MX (higher number). This prevents mail loss during maintenance or outages.
How to fix it
- 1Add a backup MX with a higher priority number (e.g., 20 or 30).
- 2The backup can be a cloud mail relay or a secondary mail server.
Code examples
DNS zone file
example.com. IN MX 10 mail.example.com. ; primary
example.com. IN MX 20 backup-mail.example.com. ; backupReferences
Detected automatically by VulnRadar. The check id is dns-mx-backup-record, stable across every scan so you can filter or diff on it.
More dns checks
Questions
- How severe is No Backup MX Server?
- VulnRadar rates this low 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-backup-record, 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.