ObsoletedPROPOSED STANDARDIETF stream

RFC 2538: Storing Certificates in the Domain Name System (DNS)

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4398.

Current version: RFC 4398Storing Certificates in the Domain Name System (DNS)

In plain English — editorial summary, not part of the RFC

Cryptographic public key are frequently published and their authenticity 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
RFC2538
Published
March 1999
Authors
D. Eastlake 3rd; O. Gudmundsson
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
10
Also known as
Obsoleted by:
RFC 4398

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.

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?

canonical URL: /rfc/2538-storing-certificates-in-the-domain-name-system-dns