Skip to content
AdminKit

OCSP stapling

What is OCSP stapling?

OCSP stapling lets a server prove its TLS certificate hasn't been revoked by attaching a signed, time-stamped response to the handshake itself, so the client doesn't have to query the certificate authority separately. AdminKit's SSL/TLS check shows a server's certificate and negotiated protocol, including whether stapling is enabled.

By AdminKit team, Netbase JSC · Updated

OCSP stapling is a way of proving a TLS certificate hasn’t been revoked without the connecting client having to contact the certificate authority itself. Normally, checking revocation with the Online Certificate Status Protocol (OCSP) means the client makes a separate request to the certificate authority’s responder every time it validates a certificate, which adds latency, leaks which sites a client visits to that authority, and fails unpredictably when the responder is slow or unreachable — OCSP itself was introduced to replace the older, poorly-scaling approach of a client downloading a whole certificate revocation list (CRL) and searching it for a serial number. With stapling, the server itself periodically fetches a signed, time-stamped OCSP response and attaches (“staples”) it directly to the TLS handshake, so the client can verify revocation status from data the server already provided, with no extra round trip or third-party query — the approach NIST’s TLS implementation guidelines recommend over a client querying the responder itself. It requires server-side support and periodic refreshing of the staple, since a stale one is treated as if no stapling happened at all; in nginx, for example, it is switched on with the ssl_stapling directive, which is off by default. The underlying revocation-checking protocol is defined in RFC 6960; the TLS extension that carries the stapled response during the handshake is defined in RFC 6066 and listed as “status_request” in IANA’s TLS ExtensionType Values registry.

OCSP stapling is part of AdminKit’s machine protocols cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

What problem does OCSP stapling solve compared to plain OCSP?

Plain OCSP means the client makes a separate request to the certificate authority's responder every time it validates a certificate, which adds latency, leaks which sites a client visits to that authority, and fails unpredictably when the responder is slow or unreachable; stapling avoids all of that by having the server attach the signed response itself.

What did OCSP itself replace?

OCSP was introduced to replace the older, poorly-scaling approach of a client downloading a whole certificate revocation list (CRL) and searching it for a serial number.

What happens if a server's stapled OCSP response goes stale?

A stale staple is treated as if no stapling happened at all, which is why it requires periodic refreshing on the server side to stay useful.

Which RFCs define OCSP stapling?

The underlying revocation-checking protocol (OCSP) is defined in RFC 6960; the TLS extension that carries the stapled response during the handshake is defined in RFC 6066.