Explicit revocation occurs when a Certificate Authority (CA) actively invalidates a digital certificate before its expiration date by adding it to a Certificate Revocation List (CRL) or updating its OCSP (Online Certificate Status Protocol) responder.
A certificate simply expires at its notAfter date; no active revocation action is needed. This is the normal lifecycle end.
It is a critical security control. Without it, a compromised certificate remains trusted until expiration—enabling man-in-the-middle attacks, identity spoofing, and data interception. Browsers and servers check CRLs/OCSP to reject explicitly revoked certificates, maintaining the trust chain.
Timely revocation and efficient distribution (via CRL caching, OCSP stapling) are essential to PKI health.