Protocols
Saved & recent

DNSSEC

Also called: DNS Security Extensions, DNS validation, DNS signatures

DNS Security Extensions let a validating resolver check the origin and integrity of DNS data using digital signatures. Signed record sets, DNS keys, and delegation records establish a chain from a configured trust anchor to the requested data. DNSSEC can also authenticate a denial that a requested name or record exists.

For example, a resolver checking an address record can verify its signature and the key’s chain of trust before accepting the signed answer. A signature mismatch is a validation failure, not an alternative address to trust. DNSSEC does not encrypt queries or answers, and a valid signature does not prove a website is harmless. DNS transport encryption solves a different problem.

Read first
DNS resolution
Related
DNS over HTTPS, DNS over TLS, Certificate
Further reading
IETF RFC 4033 — DNS Security Introduction and Requirements
trust anchor trusted DNS key signed delegation delegation / DNSKEY signed address record A 192.0.2.80 validates back to trust anchor validating resolver query: api.example.com readable query modified answer validation fails DNS data authenticity and integrity
Schematic DNSSEC validation: a chain of trust supports checks on signed DNS data, without concealing the query itself.

View in the full Protocols collection