RFC 8509: A Root Key Trust Anchor Sentinel for DNSSEC
In plain English — editorial summary, not part of the RFC
The DNS Security Extensions (DNSSEC) were developed to provide origin authentication and integrity protection for DNS data by using digital signatures. These digital signatures can be verified by building a chain of trust starting from a trust anchor and proceeding down to a particular node in the DNS. This document specifies a mechanism that will allow an end user and third parties to determine the trusted key state for the root key of the resolvers that handle that user's DNS queries. Note that this method is only applicable for determining which keys are in the trust store for the root key.
Document record
- Document ID
- RFC8509
- Published
- December 2018
- Authors
- G. Huston; J. Damas; W. Kumari
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9904DNSSEC Cryptographic Algorithm Recommendation Update ProcessCurrent
November 2025
- RFC 9905Deprecating the Use of SHA-1 in DNSSEC Signature AlgorithmsCurrent
November 2025
- RFC 9906Deprecate Usage of ECC-GOST within DNSSECCurrent
November 2025
- RFC 5910Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP)Current
May 2010
- RFC 8749Moving DNSSEC Lookaside Validation (DLV) to Historic StatusCurrent
March 2020
- RFC 8145Signaling Trust Anchor Knowledge in DNS Security Extensions (DNSSEC)Updated
April 2017
- RFC 8976Message Digest for DNS ZonesCurrent
February 2021
- RFC 8027DNSSEC Roadblock AvoidanceCurrent
November 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?