| CARVIEW |
Select Language
HTTP/2 200
date: Tue, 15 Jul 2025 05:02:29 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 95f6b52f1f068839-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 2560 » RFC Editor
Search RFCs
RFC 2560
X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP, June 1999
- File formats:
- Status:
- PROPOSED STANDARD
- Obsoleted by:
- RFC 6960
- Updated by:
- RFC 6277
- Authors:
- M. Myers
R. Ankney
A. Malpani
S. Galperin
C. Adams - Stream:
- IETF
- Source:
- pkix (sec)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC2560
Discuss this RFC: Send questions or comments to the mailing list pkix@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 2560
Abstract
This document specifies a protocol useful in determining the current status of a digital certificate without requiring CRLs. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us