How to fix: DNSSEC signed with a deprecated algorithm
The zone is DNSSEC-signed with an algorithm RFC 8624 marks as deprecated for signing. A published DNSKEY uses RSAMD5, DSA, RSA/SHA-1, one of the NSEC3 SHA-1 variants, or ECC-GOST.
Why it matters
DNSSEC is only as strong as the algorithm behind the signature, and SHA-1 and MD5 have practical collision attacks. Validating resolvers are also progressively dropping support for these algorithms entirely, and a zone signed only with a removed algorithm is treated as unsigned, which silently discards the protection the zone was configured to have.
The check reads the DNSKEY set over DNS-over-HTTPS and looks at the algorithm field of each key, so it only fires on a zone that is actually signed. RFC 8624 marks RSAMD5 as must-not-implement and the SHA-1 based algorithms as not-recommended for signing. The current recommendation is ECDSAP256SHA256 (algorithm 13), which is also far smaller on the wire than RSA, or RSASHA256 (algorithm 8) where the resolver population still needs it.
How to fix it
- 1Roll the zone to algorithm 13 (ECDSAP256SHA256), or 8 (RSASHA256) if ECDSA support is a concern for your resolver population.
- 2Follow the order: publish the new DNSKEY, re-sign the zone, wait for propagation, then update the DS record at the registrar, and only then withdraw the old key.
- 3Confirm the new chain validates end to end before removing anything.
Code examples
Inspect the zone's keys
dig +dnssec +multi DNSKEY example.com @1.1.1.1
# the third field of each DNSKEY is the algorithm numberValidate the chain after a rollover
delv @1.1.1.1 example.com A +rtrace
# or
dig +sigchase +trusted-key=./root.key example.com AReferences
Detected automatically by VulnRadar. The check id is dns-dnssec-algorithm-weak, stable across every scan so you can filter or diff on it.
More dns checks
Questions
- How severe is DNSSEC signed with a deprecated algorithm?
- 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-dnssec-algorithm-weak, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does DNSSEC signed with a deprecated algorithm map to?
- It maps to CWE-327. In the OWASP Top 10 it falls under A02: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.