Certificate Revocation in 2026: CRL, OCSP and Stapling

How Certificate Revocation Works Now: CRL, OCSP and Short-Lived Certificates (2026)
Check what the certificate itself supports before choosing a revocation-checking method. Let's Encrypt shut down its OCSP responders on 6 August 2025, having already dropped OCSP URLs from newly issued certificates on 7 May 2025, and now publishes revocation information exclusively via Certificate Revocation Lists. The CA/Browser Forum has made CRLs mandatory and OCSP optional. So the correct order is: read the AIA and crlDistributionPoints extensions → only discuss stapling if an OCSP URI exists → otherwise fetch the CRL and match the serial number → then push the residual risk down with short lifetimes and reliable automation.
Core concepts
Why revocation has always been the weakest link
Certificates expire, but a leaked private key, a misissuance or a change of affiliation means killing one early. The hard part is telling every client, near real time, without paying a privacy or availability price. Historically there were two mechanisms: bulk CRLs (the RFC 5280 profile) and per-certificate OCSP (RFC 6960). As of 2026 the ecosystem is mid-migration away from OCSP.
Why OCSP was abandoned: privacy plus cost
Let's Encrypt's primary reason is privacy: clients ask the CA about every site they visit, which is effectively handing over browsing history. Even though Let's Encrypt says it dropped that data immediately, there was no way to know whether that was standard practice across the industry, and even well-intentioned CAs could make a mistake or be compelled to save it. Cost was the second factor: in early 2025 the service handled over four billion OCSP requests per day — 180 million per hour, about 50,000 per second.
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.
Timeline, per the official announcements:
- 30 January 2025 — requests including the OCSP Must-Staple extension begin to fail, except for accounts that had previously issued such a certificate;
- 7 May 2025 — CRL URLs are added to certificates and OCSP URLs are dropped; all requests with Must-Staple now fail;
- 6 August 2025 — the OCSP responders are turned off.
What a CRL looks like today
The certificate carries a crlDistributionPoints extension pointing at an HTTP(S) URL. Download it and inspect the validity window and entry count with openssl crl. BR §4.9.7 requires CRLs to be updated at least every 7 days, with nextUpdate no later than 10 days after thisUpdate (confirm against the official CA/Browser Forum document). CRLs grow with revocation volume — the very reason OCSP was invented.
Should you still enable OCSP stapling?
Stapling has the server fetch the signed response from the CA and attach it to the TLS handshake, so visitors never contact the CA: faster and more private. It is defined in RFC 6066 §8, and RFC 6961 extended it to intermediate certificates via status_request_v2, which TLS 1.3 deprecates RFC 8446 §4.2. The practical constraint: no OCSP URI in the certificate means nothing to staple. If all your certificates come from Let's Encrypt, stapling configuration is now inert — audit your config and monitoring for stale OCSP assumptions. Separately, Chrome 148 (2026-05-05) removed support for conveying SCTs via OCSP stapling (per Chrome release notes).
What browsers actually do — and why short lifetimes are the real workhorse
Major browsers do not fetch CRLs or query OCSP in real time; they rely on locally delivered compressed data and treat short lifetimes as the primary risk reducer. Consequences: after you revoke, some clients may still accept the certificate for a while. That is by design, not a misconfiguration on your side.
Short lifetimes are the real workhorse: SC-081v3 compresses the maximum lifetime of publicly trusted TLS server certificates in steps: 200 days from 2026-03-15, 100 days from 2027-03-15, 47 days from 2029-03-15 (per official announcements); Let's Encrypt additionally plans 64 days on 2027-02-10 and 45 days on 2028-02-16. At lifetimes measured in weeks, revocation urgency is largely absorbed by automated renewal — provided your automation is actually reliable.
Where each mechanism stands (2026), and the end of expiry emails
| Mechanism | Status | Entry point |
|---|---|---|
| CRL | Mandatory; BR §4.9.7 requires updating at least every 7 days, with nextUpdate no more than 10 days after thisUpdate (confirm against the official BR text) | openssl x509 -noout -ext crlDistributionPoints |
| OCSP | Optional in the BRs since March 2024; fully retired at Let's Encrypt | openssl x509 -noout -ocsp_uri (empty means none) |
| OCSP stapling | Defined in RFC 6066 §8; RFC 6961 extended it to intermediate certificates via status_request_v2, which TLS 1.3 deprecates RFC 8446 §4.2 | openssl s_client -status |
| Must-Staple | Let's Encrypt began failing these requests on 30 January 2025 and fails all of them from 7 May 2025 | — |
| Short lifetimes | SC-081v3: 200 days from 2026-03-15, 100 days from 2027-03-15, 47 days from 2029-03-15; Let's Encrypt additionally plans 64 days on 2027-02-10 and 45 days on 2028-02-16 (per official announcements) | openssl x509 -noout -dates |
A side change that catches teams out: expiry emails are gone. Let's Encrypt ended its expiration notification email service on 4 June 2025. Teams that relied on it as a safety net must switch to monitoring, or a failed renewal surfaces as an outage.
Step by step
Step 1 — Find out what this certificate offers
openssl s_client -connect example.com:443 -servername example.com </dev/null 2>/dev/null \
| openssl x509 -noout -text | grep -A3 "Authority Information Access\|CRL Distribution"Or field by field:
openssl x509 -in leaf.pem -noout -ocsp_uri # empty = no OCSP for this certificate
openssl x509 -in leaf.pem -noout -ext crlDistributionPointsNo terminal handy? The Certificate Decoder shows the extensions in your browser.
Step 2 — Fetch the CRL and check its freshness window
CRL=$(openssl x509 -in leaf.pem -noout -ext crlDistributionPoints | grep -oE 'https?://[^ ]+')
curl -s -o crl.der "$CRL"
openssl crl -in crl.der -inform DER -noout -lastupdate -nextupdate
openssl crl -in crl.der -inform DER -noout -text | grep -c "Serial Number:"The span from lastUpdate to nextUpdate is how long this blacklist stays fresh; if nextUpdate has passed without a refresh, your revocation view is stale.
Step 3 — Match the serial number
SER=$(openssl x509 -in leaf.pem -noout -serial | cut -d= -f2)
openssl crl -in crl.der -inform DER -noout -text \
| grep -iE "^[[:space:]]*Serial Number:[[:space:]]*0*${SER}$" \
&& echo "REVOKED" || echo "not in this CRL""not in this CRL" means exactly that — it does not mean the certificate is trustworthy. Pair it with the Certificate & Key Matcher and the incomplete chain troubleshooting guide.
Step 4 — Only verify stapling when an OCSP URI exists
openssl s_client -connect example.com:443 -servername example.com -status </dev/null 2>/dev/null \
| grep -A5 "OCSP Response Status"If Step 1 returned an empty -ocsp_uri, no response is possible; clean up the configuration instead of debugging it repeatedly. To enable stapling: Nginx ssl_stapling on; ssl_stapling_verify on; plus ssl_trusted_certificate containing intermediates; Apache SSLUseStapling on. Quick audit: SSL Checker, Certificate Decoder.
Step 5 — Order of operations for a leaked private key
Revoke first (an ACME account can revoke with a request signed by the certificate's own key):
certbot revoke --cert-path /etc/letsencrypt/live/example.com/cert.pem --reason keycompromise- Reissue with a brand new key pair — never reuse the old private key.
- Deploy and reload, then confirm the new serial number is live and the chain is complete.
- Look back through CT logs for certificates you did not request — see certificate transparency logs.
- Tighten issuance with CAA and account binding — see CAA records.
Step 6 — Replace expiry emails with active monitoring
Since the email service ended, cover it with a local cron job checking remaining days, external synthetic monitoring, or periodic checks with the Let's Encrypt expiry checker.
Troubleshooting checklist
| Symptom | Cause | Fix |
|---|---|---|
| openssl x509 -noout -ocsp_uri returns nothing | Not a bad command — Let's Encrypt stopped including OCSP URLs on 7 May 2025, so a 2026-issued certificate legitimately has none | Switch to the CRL workflow |
| ERR_CERT_REVOKED | The certificate really is revoked | Follow Step 5; do not try to bypass it |
| Nginx/Apache warnings about stapling | With no OCSP URI there is nothing to staple | Remove the directives rather than debugging them |
| CRL download fails or times out | Strict clients may fail the connection | Check egress firewall and DNS |
| nextUpdate already passed | The CRL is stale and your revocation view is unreliable | Check against the BR §4.9.7 update cadence with the CA |
| Old certificate still served after revocation | Clients rely on locally delivered data, so delay is normal | Also check for stale copies on your CDN or load balancer |
| Nobody noticed a failed renewal | Expiry emails stopped on 4 June 2025 | Build your own alerting (cron, external monitoring, expiry checker) |
| Mass failures after an ACME account change | You also use CAA accounturi and DNS was not updated | Update DNS in the same change; see CAA records |
| Unsure which extensions a certificate carries | PEM/DER confusion or overlooked extensions | Sort out conversion first with the certificate formats guide |
| Private key may have leaked but you cannot confirm | Exposure cannot be ruled out | Treat it as leaked. Revoking and rotating is far cheaper than staying exposed |
Next step
Use the Let's Encrypt expiry checker to confirm remaining lifetime and chain state, then the SSL certificate selector to evaluate whether a commercial certificate with a different revocation profile fits better. Revocation and issuance are two sides of the same coin, so read CAA Records Explained alongside this.
Tools: SSL Checker for a live audit · Certificate Decoder for extensions · Certificate & Key Matcher to rule out pairing issues
Related: CAA Records Explained · Certificate Transparency Logs Explained · SSL Certificate Formats Explained
Go deeper: SSL certificate guide · Certificate brands
FAQ
Do browsers actually check revocation?
Major browsers rely mostly on locally delivered compressed data plus short lifetimes, not real-time CRL fetches or OCSP queries. After you revoke, some clients may still accept the certificate for a while — that is by design.
How do I check revocation for a Let's Encrypt certificate now?
Only via the CRL named in crlDistributionPoints; the OCSP responders were switched off on 6 August 2025.
Is OCSP stapling still worth enabling?
Only if the certificate has an OCSP URI. If it does, stapling is faster and leaks nothing about visitors; Let's Encrypt certificates have none, so there is nothing to staple.
Can I still use Must-Staple?
Not with Let's Encrypt: those requests started failing on 30 January 2025 and fail universally from 7 May 2025.
With lifetimes shrinking, can I ignore revocation?
Not ignore, but the exposure is much smaller — assuming renewal automation is reliable and monitored, because expiry emails no longer exist.
Free SSL/TLS tools
Verify and inspect your certificates in seconds.
Related Certificate Info
Learn more about choosing and buying certificates.