Skip to main content
InfoDNSOWASP A05:2021CWE-400

How to fix: NSEC3 configured with extra hash iterations

The zone's NSEC3PARAM record declares a non-zero iteration count. RFC 9276 says the only value that should be used is zero.

Why it matters

Every extra iteration costs the authoritative server and every validating resolver an additional hash computation on each negative answer, and provides no meaningful additional protection against enumeration. That turns the parameter into a denial-of-service amplifier aimed at your own nameservers: an attacker querying random non-existent names forces the extra work on every request.

The original NSEC3 specification allowed iterations as a defence against dictionary attacks on the hashed names, but the protection turned out to be negligible because the name space being hashed is small and guessable regardless. RFC 9276 is unambiguous: zero iterations, empty salt. Several large resolvers now cap or ignore high iteration counts, and some treat zones above a threshold as insecure, so a high value can cost validation as well as performance.

How to fix it

  1. 1Set the NSEC3 iteration count to 0 and use an empty salt, then re-sign the zone.
  2. 2Most managed DNS providers expose this as a single setting; on BIND it is the iterations argument to the NSEC3 parameters.
  3. 3Confirm the zone still validates after re-signing.

Code examples

Read the current parameters

bash
dig +short NSEC3PARAM example.com
# fields: hash flags iterations salt

BIND: zero iterations, no salt

bash
rndc signing -nsec3param 1 0 0 - example.com

References

Detected automatically by VulnRadar. The check id is dns-nsec3-iterations-nonzero, stable across every scan so you can filter or diff on it.

See every dns check

Questions

How severe is NSEC3 configured with extra hash iterations?
VulnRadar rates this info 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-nsec3-iterations-nonzero, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does NSEC3 configured with extra hash iterations map to?
It maps to CWE-400. In the OWASP Top 10 it falls under A05: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.

Propose a checkHow a check is built

Scan your own site for nsec3 configured with extra hash iterations

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

NSEC3 configured with extra hash iterations fix | VulnRadar