Network

OCSP stapling

The server fetches a signed revocation status for its own certificate and sends it in the TLS handshake, sparing clients a lookup.

OCSP (RFC 6960) lets a client ask a CA whether a certificate is revoked. Asking live is slow, leaks browsing to the CA, and browsers soft-fail when the responder is down, so an attacker who blocks OCSP wins. With stapling, the server periodically fetches a signed, time-limited OCSP response and attaches it to the handshake via the TLS status request extension.

Must-Staple (RFC 7633) marks a certificate as requiring a stapled response, turning soft-fail into hard-fail, but adoption stayed low because server stapling implementations were fragile.

The industry has largely moved on: CA/Browser Forum rules made OCSP optional for public CAs and Let's Encrypt shut down its OCSP service in 2025, relying on CRLs and ever shorter certificate lifetimes instead. Expect to discuss this trade-off, not to recommend stapling by reflex.

Learn it properly

Also used in

Related terms