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

HTTP proves control of a path

03

The client publishes a key authorization at a server-chosen challenge path.

Related RFCs and changes

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

DIAGRAM§ 8.3 ↗
RFC 8555 · § 8.3EXAMPLE
3 / 3
HTTP proves control of a pathThe client publishes a key authorization at a server-chosen challenge path. Current state: Compare.HTTP proves control of a pathACME clientCA/.well-known/acme-challenge/TOKENkey authorizationHTTP · port 80expected key authorization matches
03
Compare

Correct content satisfies the challenge; an unrelated page does not.

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

http-01 uses the /.well-known/acme-challenge/ path.

  • http-01 uses the /.well-known/acme-challenge/ path.
  • The check is performed over HTTP on port 80.
  • The published value binds the challenge token to the account key.
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 ↗