CRL (certificate revocation list)
What is CRL (certificate revocation list)?
A certificate revocation list (CRL) is a certificate authority's signed, periodically published list of certificate serial numbers it has revoked before their stated expiry, defined in RFC 5280's X.509 standard. AdminKit's SSL check tool shows a live certificate's details, including which revocation mechanism -- CRL or OCSP -- it actually references.
By AdminKit team, Netbase JSC · Updated
A certificate revocation list (CRL) is a signed, periodically published list of certificate serial numbers a certificate authority has revoked before their stated expiry, defined as part of the X.509 standard in RFC 5280 (also tracked on the IETF Datatracker). A client that wants to confirm a certificate hasn’t been revoked downloads the current CRL from a URL the certificate itself specifies and checks whether the certificate’s serial number appears on it — a model that scales poorly as a CA’s revoked-certificate count grows, since every check requires fetching and searching a potentially large, slowly updated list. OCSP was introduced specifically to replace this per-certificate lookup with a single targeted query, and OCSP stapling went further by letting the server supply that proof itself; even so, CRLs remain a mandatory revocation mechanism the CA/Browser Forum’s own Baseline Requirements impose on every publicly-trusted CA, and some clients and CAs still rely on them as the primary revocation mechanism. Let’s Encrypt is one: in December 2024 it announced it would provide revocation information exclusively via CRLs, citing their significant advantages over OCSP, and set August 6, 2025 as the date to turn off its OCSP responders. None of this applies to a self-signed certificate, though: with no CA standing behind it, there’s no CRL to check it against in the first place.
CRL vs. OCSP, at a glance:
- CRL: the client downloads a whole list and searches it for a serial number — simple, but scales poorly.
- OCSP (RFC 6960): a single targeted query per certificate, instead of fetching the whole list.
- OCSP stapling: the server supplies the proof itself, so the client never has to query anything.
AdminKit groups cRL (certificate revocation list) under its machine protocols cluster — browse the AdminKit glossary index for other related terms.
Frequently asked questions
Why doesn't a CRL scale well?
A client checking a CRL downloads the current list from a URL the certificate itself specifies and searches it for the certificate's serial number -- every check requires fetching and searching a potentially large, slowly updated list, which gets more expensive as a CA's revoked-certificate count grows.
What replaced the per-certificate CRL lookup?
OCSP (RFC 6960) was introduced specifically to replace it with a single targeted query per certificate, instead of fetching the whole list. OCSP stapling went further by letting the server supply that proof itself.
Are CRLs still used even though OCSP exists?
Yes -- CRLs remain a required fallback in the X.509 standard, and some clients and CAs still rely on them as the primary revocation mechanism.
Does a self-signed certificate have a CRL to check against?
No -- with no CA standing behind a self-signed certificate, there's no CRL to check it against in the first place.
Sources
- RFC 5280 -- Internet X.509 Public Key Infrastructure Certificate and CRL Profile
- RFC 6960 -- X.509 Internet PKI Online Certificate Status Protocol (OCSP)
- IETF Datatracker -- RFC 5280 (X.509 Certificate and CRL Profile) document status
- CA/Browser Forum -- Baseline Requirements for the Issuance and Management of Publicly-Trusted TLS Certificates
- Ending OCSP Support in 2025 - Let's Encrypt