Visual RFC.
ALL RFCs / RFC 8555
Read the RFC ↗
RFC 8555 / MECHANISMS

DNS proves control of a record

04

A TXT record carries a digest of the challenge’s key authorization.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 8.4 ↗
RFC 8555 · § 8.4EXAMPLE
3 / 3
DNS proves control of a recordA TXT record carries a digest of the challenge’s key authorization. Current state: CA resolves.DNS proves control of a recordkey authorizationSHA-256base64url digest_acme-challengeexample.orgTXT = digestpublishCA resolves TXT
03
CA resolves

The expected TXT value proves the required control for this challenge.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

dns-01 uses a name under _acme-challenge.

  • dns-01 uses a name under _acme-challenge.
  • The TXT value is the base64url-encoded SHA-256 digest of the key authorization.
  • The CA checks the record against the expected value.
DETAILS

The illustration is schematic. Example values are illustrative; profiles and later security guidance can add requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. An order is a state machine
  2. One nonce for one signed request
  3. HTTP proves control of a path
  4. DNS proves control of a record
  5. CSR, certificate, and revocation

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗