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

A certificate binds a public key

01

The signed certificate body binds a subject and other information to a public key.

Related RFCs and changes

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

DIAGRAM§ 4.1 ↗
RFC 5280 · § 4.1EXAMPLE
3 / 3
A certificate binds a public keyThe signed certificate body binds a subject and other information to a public key. Current state: Trust needed.A certificate binds a public keyTBSCertificateissuer · subjectnotBefore / notAfterpublic keyextensionstrusted issuer?path validation
03
Trust needed

The verifier still needs a valid path and an appropriate trust anchor.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 3280RFC 5280 § 1

This profile replaces RFC 3280 and incorporates the intervening RFC 4325 and RFC 4630 updates.

Read the updated RFC section ↗
KEY POINT

A certificate contains TBSCertificate, a signature algorithm, and a signature value.

  • A certificate contains TBSCertificate, a signature algorithm, and a signature value.
  • The issuer signs the encoded TBSCertificate.
  • Reading a subject name is not the same as trusting it.
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. A certificate binds a public key
  2. A chain ends at configured trust
  3. Extensions constrain authority
  4. Validity is a bounded interval
  5. Revocation is separate evidence
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗