How to fix: DNSSEC Not Enabled
DNSSEC is not enabled for this domain's DNS zone. Without DNSSEC, DNS responses can be forged by cache poisoning attacks, redirecting email to attacker-controlled servers.
Why it matters
Without DNSSEC, attackers can poison DNS caches to forge MX records, redirecting inbound email to attacker-controlled mail servers. SPF and DMARC DNS lookups can also be spoofed, undermining email authentication.
DNSSEC (RFC 4034/4035) uses public-key cryptography to sign DNS records. When DNSSEC is enabled and a DS record is published at the parent TLD, DNSSEC-validating resolvers can verify that DNS responses have not been tampered with. This is particularly important for email since MX, SPF, DKIM, and DMARC all rely on DNS lookups.
How to fix it
- 1Enable DNSSEC in your DNS provider's control panel or configure it in BIND/Knot/PowerDNS.
- 2Submit the DS record to your domain registrar.
- 3Verify: dig +dnssec A example.com (look for 'ad' flag and RRSIG records)
Code examples
Verify DNSSEC status
dig +dnssec A example.com | grep -E '(RRSIG|flags.*ad)'References
Detected automatically by VulnRadar. The check id is dnssec-enabled, stable across every scan so you can filter or diff on it.
More email checks
- LowDMARC Forensic Report URI (ruf=) Missing
- MediumDMARC Aggregate Report URI (rua=) Missing
- MediumMTA-STS (SMTP Strict Transport Security)
- LowTLS-RPT Record Missing rua= Reporting URI
- HighSPF Exceeds 10 DNS Lookup Limit
- HighSPF Redirect Loop
- LowDMARC pct= Below 100
- MediumDMARC Policy Set to Monitor-Only (p=none)
Questions
- How severe is DNSSEC Not Enabled?
- VulnRadar rates this info severity in the email 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 dnssec-enabled, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does DNSSEC Not Enabled map to?
- It maps to CWE-345. In the OWASP Top 10 it falls under A08:2021.
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.