Back to Articles
Guide2026-07-08•5 min read•CSR.plus Team

What Is OCSP Stapling? 2026 Status and Setup

What Is OCSP Stapling? 2026 Status and Setup
2025-08-06
Let's Encrypt OCSP shutdown
Let's Encrypt announcement
~340B/month
Peak traffic before shutdown
OCSP requests (Let's Encrypt, 2025-08)
2026-05-05
Chrome 148
Removes OCSP-delivered SCTs
47 days
Lifetime cap
Cap from 2029-03-15 (CA/Browser Forum SC-081v3)

What Is OCSP Stapling? How It Works and Where It Stands in 2026

OCSP stapling lets your web server attach a CA-signed, time-stamped revocation proof to the TLS handshake, so browsers never contact the CA online — one round trip saved and visitor IPs kept private. The ecosystem, however, is retreating: Let's Encrypt turned off its OCSP responders on 2025-08-06 and now publishes revocation data only via CRLs, Chrome 148 (2026-05-05) removed OCSP-delivered SCTs, and maximum certificate lifetimes are down to 200 days and falling. This guide explains how stapling works, how to configure it on Nginx, Apache and Caddy, and whether it is still worth enabling in 2026.

What OCSP does

OCSP (Online Certificate Status Protocol) is how browsers check whether a certificate has been revoked before trusting it: the browser asks the CA's responder "is this certificate still valid?" and receives a signed yes/no answer. Without revocation checking, a compromised or revoked certificate would stay trusted until it expires. But online checking has side effects — traditional OCSP has three problems: an extra network round trip on every new connection, a fragile dependency on responder availability (browsers must choose between failing the connection and soft-fail), and the visitor's IP address being revealed to the CA.

How stapling works: the status_request extension of RFC 6066

OCSP stapling is standardized as the status_request extension in section 8 of TLS extension RFC 6066: the web server periodically fetches (typically every few hours) a time-stamped, CA-signed status response, caches it locally, and "staples" it to its own messages during the TLS handshake. The browser verifies the signature without contacting the CA — saving a round trip and the privacy leak. RFC 6961 later defined an extension for stapling the status of multiple certificates in a chain (stapling v2), but adoption stayed limited.

2026 status: OCSP is retreating

The timeline is clear: Let's Encrypt announced its intent to end OCSP on 2024-07-23, stopped including OCSP URLs in certificates on 2025-05-07, and turned off its responders on 2025-08-06, publishing revocation information exclusively via CRLs since then (Let's Encrypt official announcements). Its OCSP service peaked at roughly 340 billion requests per month. Chrome 148 (2026-05-05) removed OCSP-delivered SCTs, further shrinking OCSP's role. Meanwhile, CA/Browser Forum ballot SC-081v3 caps certificate validity at 200 days from 2026-03-15, falling to 47 days by 2029 — the shorter the certificate, the less revocation checking matters. Commercial CAs still run OCSP, and stapling keeps working with their certificates.

Let's Encrypt: OCSP end-of-life, 2025-08-06 · Let's Encrypt: 2025 end-of-year letter — peak monthly OCSP requests vs. daily request rate, two different metrics.

Why Must-Staple never took off

Must-Staple is a certificate extension telling browsers to refuse connections unless a stapled response is present — designed to close the soft-fail gap. After years of limited browser support and repeated web-server stapling failures, Let's Encrypt stopped issuing Must-Staple certificates on 2025-05-07. Everyday sites should not rely on it.

Step 1: Check whether your certificate still has an OCSP URL

Open the Certificate Decoder and inspect the AIA extension. If — like Let's Encrypt certificates — there is no OCSP URL, remove stapling from your server config and let revocation go through CRLs (verify with the Revocation Checker).

Step 2: Enable or clean up the server configuration

Nginx (when the certificate still has an OCSP URL):

ssl_stapling on;
ssl_stapling_verify on;

Make sure ssl_certificate points to the full chain including intermediates. Apache uses SSLUseStapling On plus a stapling cache directive. Caddy handles it automatically. With Let's Encrypt certificates, simply remove these directives.

Step 3: Verify the handshake

Use the SSL/TLS Tracer to check whether the handshake carries a stapled OCSP response and its validity window, or run:

openssl s_client -connect yourdomain.com:443 -status

The OCSP response section confirms the server is stapling correctly.

Step 4: Rethink your revocation strategy

In the short-lifetime era, revocation is shifting from online OCSP queries to CRL distribution plus automated rotation. Make sure your ACME client renews automatically — do not pin your security to a single revocation mechanism.

Troubleshooting checklist

SymptomLikely causeFix
Nginx logs "ssl_stapling ignored"Certificate has no OCSP URL or chain incompleteRemove the directive for Let's Encrypt; complete the chain for commercial certs
No stapled response in the handshakeServer cannot reach the OCSP responderCheck outbound network and firewall rules
openssl -status shows no OCSP sectionStapling not enabled or unsupportedRecheck config and certificate per Step 2
Browser warns revocation status unknownResponder unreachable, browser soft-failsConfirm the CRL distribution point is reachable and rotating
Must-Staple certificate fails to renewLet's Encrypt stopped issuing them on 2025-05-07Drop the mustStaple request and re-issue
No OCSP field in the decoded certificateNew certificate profiles omit OCSP URLsUse CRL-based revocation checking instead

Take action

Related: Certificate Revocation: OCSP and CRLs, Certificate Transparency Logs, CAA Records.

FAQ

What is the difference between OCSP and OCSP stapling?

OCSP is the protocol by which a browser queries the CA online for a certificate's revocation status. OCSP stapling — built on the status_request extension of RFC 6066 — moves that CA-signed, time-stamped response into the server's handshake message, so the browser never contacts the CA.

Is OCSP stapling still worth enabling in 2026?

It depends on the certificate. Let's Encrypt certificates have contained no OCSP URL since 2025-05-07, so there is nothing to staple — remove the config. Certificates from commercial CAs still come with OCSP service, where stapling remains an optional privacy and latency optimization.

Why did Let's Encrypt shut down its OCSP service?

Two official reasons: OCSP queries reveal visitor IP addresses to the CA, a privacy risk; and running OCSP responders consumed enormous resources. Since 2025-08-06, Let's Encrypt publishes revocation information exclusively via CRLs.

Does OCSP Must-Staple still work?

Let's Encrypt stopped issuing Must-Staple certificates on 2025-05-07, and the extension never gained broad browser support. If you genuinely need it, use a commercial CA that still honors it.

How do I verify my OCSP stapling setup?

Use the [SSL/TLS Tracer](/tools/ssl-tracer) to see whether the handshake carries a stapled response, or run `openssl s_client -connect yourdomain.com:443 -status` and check the OCSP response section; the [Certificate Decoder](/tools/cert-inspector) shows whether your certificate still has an OCSP URL at all.

Free SSL/TLS tools

Verify and inspect your certificates in seconds.

Related Certificate Info

Learn more about choosing and buying certificates.

Related articles