Certificate Authorities and Trust Chains
You'll learn how browsers verify that a website's digital certificate is legitimate by following a chain of trusted authorities back to a root CA.
The Trust Problem
Remember that digital certificates link a public key to a domain name or entity. But how does your browser know that certificate is real and not forged by an attacker? This is where Certificate Authorities (CAs) come in.
Certificate Authorities
A Certificate Authority is a trusted third-party organization that issues digital certificates. Think of a CA like a passport office: just as a government passport office verifies your identity and issues a passport that others trust, a CA verifies a website owner's identity and issues a certificate that browsers trust.
Popular CAs include DigiCert, Let's Encrypt, and GlobalSign.
The Chain of Trust
Certificates form a trust chain (or certificate chain):
- End-entity certificate: The actual website's certificate (e.g., for
example.com) - Intermediate certificate(s): Issued by a CA to sign end-entity certificates
- Root certificate: Self-signed certificate from the root CA, pre-installed in your browser or operating system
When you visit an HTTPS site, your browser:
- Receives the website's certificate
- Checks who signed it (the intermediate CA)
- Checks who signed that certificate (moving up the chain)
- Continues until reaching a root certificate it already trusts
If any link breaks (invalid signature, expired certificate, or untrusted root), the connection fails with a security warning.
Why Use Intermediates?
Root certificates are kept extremely secure (often offline). Intermediate certificates do the day-to-day work of signing website certificates, limiting risk if compromised.
Key Takeaway: Certificate Authorities issue trusted digital certificates, and browsers verify them by walking up a chain of signatures until reaching a pre-trusted root certificate—establishing authenticity without prior direct trust in each website.