RFC 4398: Storing Certificates in the Domain Name System (DNS)
In plain English — editorial summary, not part of the RFC
Cryptographic public keys are frequently published, and their authenticity is demonstrated by certificates. A CERT resource record (RR) is defined so that such certificates and related certificate revocation lists can be stored in the Domain Name System (DNS). [STANDARDS-TRACK]
Document record
- Document ID
- RFC4398
- Published
- March 2006
- Authors
- S. Josefsson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 17
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1994PPP Challenge Handshake Authentication Protocol (CHAP)Updated
August 1996
- RFC 4641DNSSEC Operational PracticesObsoleted
September 2006
- RFC 2797Certificate Management Messages over CMSObsoleted
April 2000
- RFC 2744Generic Security Service API Version 2 : C-bindingsUpdated
January 2000
- RFC 2743Generic Security Service Application Program Interface Version 2, Update 1Updated
January 2000
- RFC 2659Security Extensions For HTMLCurrent
August 1999
- RFC 2541DNS Security Operational ConsiderationsObsoleted
March 1999
- RFC 2539Storage of Diffie-Hellman Keys in the Domain Name System (DNS)Updated
March 1999
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?