The Certificate Chain of Trust
What you'll learn: How browsers verify that a website's certificate is genuinely trustworthy by tracing a chain from a root authority down to the server's certificate.
The Trust Problem
When your browser connects to https://example.com, the server presents a digital certificate saying "I am example.com." But how does your browser know this certificate is legitimate and not forged by an attacker? The answer lies in the certificate chain of trust.
How the Chain Works
Think of it like verifying someone's identity through mutual friends. You trust your close friend (root CA), who vouches for their colleague (intermediate CA), who vouches for the stranger (server certificate).
The chain typically has three levels:
-
Root Certificate Authority (Root CA): Pre-installed in your browser/OS. These are organizations like DigiCert, Let's Encrypt, or GlobalSign that browsers inherently trust.
-
Intermediate Certificate Authority: Issued by the root CA. Root CAs rarely sign server certificates directly—they delegate to intermediates for security (if an intermediate is compromised, only it needs replacement, not the root).
-
Server Certificate: The actual certificate for
example.com, signed by an intermediate CA.
Verification Process
When verifying, your browser:
- Checks the server certificate's signature using the intermediate CA's public key
- Checks the intermediate certificate's signature using the root CA's public key
- Confirms the root CA is in its trusted store
- Validates certificate expiration dates and revocation status at each level
If any link breaks—expired certificate, revoked intermediate, or untrusted root—the chain fails and the browser shows a security warning.
Key Takeaway: The certificate chain of trust allows browsers to verify server certificates by following cryptographic signatures from a trusted root CA through intermediates to the server, ensuring secure HTTPS connections.