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

Validity is a bounded interval

04

A certificate’s notBefore and notAfter fields describe its validity period.

Related RFCs and changes

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

RFC 5280 · § 4.1.2.5EXAMPLE
3 / 3
Validity is a bounded intervalA certificate’s notBefore and notAfter fields describe its validity period. Current state: After notAfter.Validity is a bounded intervalnotBeforenotAfterexpiredThe validity endpoints are included; other checks remain necessary.
03
After notAfter

The certificate has expired.

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

The validity interval includes both endpoints.

  • The validity interval includes both endpoints.
  • Path validation checks validity at the validation time.
  • A currently valid date does not prove the certificate is unrevoked or trusted.
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 ↗