DNSSEC
— Domain Name System Security ExtensionsDNSSEC adds digital signatures to DNS data so a resolver can prove that an answer really came from the authoritative zone and was not altered in transit. It provides origin authentication and integrity, but it does not encrypt queries or responses.
Interactive Session: How DNSSEC Works
Step through the packet exchange sequence between nodes.
Interactive Execution Sandbox
Interact with a live or clearly-labelled simulated instance of DNSSEC.
Threat Model & Attack Simulation
How this protocol is attacked in practice, what defenders can see, and which control stops it.
Threat model & attack simulation
SimulatedDefensive education. Every step runs in this page; no traffic is generated or sent.
DNSSEC downgrade and zone walking
DowngradeStripping the DO bit or querying NSEC records can bypass validation or enumerate a zone.
Strip validation
An on-path attacker removes DNSSEC records so a non-validating resolver accepts the answer.
Answers with missing RRSIG or DO.
Spoofed answers and information disclosure.
Defences that matter
- Enforce validating resolvers
- Use NSEC3 with opt-out where appropriate
- Do not rely on DNSSEC alone for confidentiality
This is a conceptual model for defenders, not an exploit toolkit. It contains no payloads, tooling or instructions for attacking systems you do not own.
Protocol Specification & Architecture
Key characteristics, real-world deployment patterns, and trade-offs.
Core Technical Features
- RRSIG records carrying a cryptographic signature over each resource record set
- DNSKEY records holding the zone signing keys, with KSK and ZSK roles
- DS records in the parent zone that link a child zone into the chain of trust
- Authenticated denial of existence through NSEC or NSEC3 records
Real-World Use Cases
- Protecting banks and governments against DNS cache poisoning
- Validating resolver deployments such as Unbound or BIND
- Securing mail and service discovery records against tampering
Advantages & Strengths
- Detects forged or modified DNS answers before applications use them
- Backward compatible, since unsigned zones still resolve without validation
Limitations & Vulnerabilities
- Does not provide confidentiality, so queries and answers remain readable
- Key rollover and chain-of-trust mistakes can make an entire zone unreachable