How to fix: DNSSEC DS record uses only the SHA-1 digest
The DS record set in the parent zone contains a SHA-1 digest (type 1) and no SHA-256 or SHA-384 alternative alongside it.
Why it matters
The DS digest is the single link between the parent zone and this zone's key. Validators that stop accepting SHA-1 digests, which is the direction every implementation is heading, will treat the delegation as unsigned and silently drop DNSSEC protection for the entire zone.
RFC 8624 marks SHA-1 as not-recommended for DS records and SHA-256 (digest type 2) as mandatory to implement. A zone publishing both digests is mid-rollover and validators use the stronger one, so that case is deliberately not reported here. Note that the DS record lives in the parent zone, so this is changed at the registrar rather than in your own DNS.
How to fix it
- 1Generate a SHA-256 DS record from the current key-signing key and submit it to the registrar.
- 2Publish both digests during the transition, then remove the SHA-1 one once the new record has propagated.
- 3Re-check the delegation validates before removing the old digest.
Code examples
Generate a SHA-256 DS record
dig DNSKEY example.com | dnssec-dsfromkey -f - -2 example.comCheck what the parent publishes
dig +short DS example.com @1.1.1.1
# fields: keytag algorithm digest-type digestReferences
Detected automatically by VulnRadar. The check id is dns-ds-digest-algorithm-weak, stable across every scan so you can filter or diff on it.
More dns checks
Questions
- How severe is DNSSEC DS record uses only the SHA-1 digest?
- 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-ds-digest-algorithm-weak, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does DNSSEC DS record uses only the SHA-1 digest 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.