Skip to content
AdminKit

NSEC record

What is NSEC record?

NSEC, defined in RFC 4034 and RFC 4035, is the original DNSSEC record that proves a DNS name genuinely doesn't exist by naming the next real owner name in the zone -- which also lets anyone walk the chain and enumerate it. AdminKit's DNSSEC guide covers the signature chain NSEC plugs into.

By AdminKit team, Netbase JSC · Updated

NSEC is the original DNSSEC record type, defined in RFC 4034 (a Proposed Standard per its IETF Datatracker entry) and RFC 4035, that lets a resolver cryptographically confirm a queried name genuinely doesn’t exist in a signed zone — authenticated denial of existence — rather than trusting an unsigned negative response. Cloudflare’s explanation of how DNSSEC works frames the same gap plainly: an unsigned “no such name” answer can’t be authenticated because there’s no record to sign, which is the problem NSEC and NSEC3 both solve. Each NSEC record names the next owner name that actually exists in the zone’s canonical sort order, plus a bitmap of which record types exist at the current name, so a signed NSEC record proving no name falls between two neighbors also proves a queried name in that gap isn’t a forged answer. The tradeoff is built into the mechanism: because the chain links real, sequential owner names, anyone can query it record by record and reconstruct the zone’s entire name list, even names never otherwise published — zone enumeration, or zone walking. Microsoft’s DNSSEC overview for Windows Server defines zone walking the same way: “the process of repeating NSEC queries in order to retrieve all the names in a zone.” NSEC3 closes that gap by replacing each owner name with a salted hash, so the same proof no longer reveals what the zone actually contains.

NSEC record is part of AdminKit’s DNS cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

What does an NSEC record prove?

That a queried DNS name genuinely doesn't exist in a signed zone, by naming the next real owner name that actually exists in the zone's canonical sort order.

What is the tradeoff of using NSEC?

Because the chain links real, sequential owner names, anyone can query it record by record and reconstruct the zone's entire name list -- zone enumeration, or zone walking.

What replaced NSEC to fix zone enumeration?

NSEC3, which replaces each owner name with a salted hash so the same denial-of-existence proof no longer reveals the zone's contents.

Which RFCs define NSEC?

RFC 4034 and RFC 4035, part of the core DNSSEC specification set.