Certificate Validation Process
What you'll learn: How browsers systematically verify that a server's digital certificate is trustworthy before establishing a secure HTTPS connection.
Why Validation Matters
When your browser receives a certificate from a server during the TLS handshake, it can't just take the certificate at face value. The validation process ensures the certificate is legitimate, current, and hasn't been compromised—like checking that a passport is genuine, not expired, and hasn't been reported stolen.
The Three Core Validation Steps
1. Signature Verification
The browser verifies that the certificate was actually signed by a trusted Certificate Authority (CA). It does this by:
- Following the trust chain from the server's certificate up to a root CA in the browser's trusted store
- Using the CA's public key to decrypt and verify each signature in the chain
- Confirming that each signature mathematically matches the certificate's contents
2. Expiration Check
Certificates contain "valid from" and "valid until" timestamps. The browser checks that the current date/time falls within this validity window. An expired certificate is rejected immediately—like a driver's license that's no longer valid.
3. Revocation Check
Even valid certificates can be revoked if compromised (private key leaked) or no longer trusted. Browsers verify revocation status through:
- Certificate Revocation Lists (CRLs): Downloadable lists of revoked certificate serial numbers
- Online Certificate Status Protocol (OCSP): Real-time queries to check individual certificates
If any step fails, the browser displays a security warning and typically blocks the connection.
Key Takeaway: Certificate validation combines signature verification (proving authenticity), expiration checks (ensuring timeliness), and revocation checks (confirming the certificate hasn't been compromised) to establish trust before any encrypted data is exchanged.