Digital Certificates and Certificate Authorities
What you'll learn: How X.509 digital certificates prove a server's identity and how Certificate Authorities validate them to enable trust on the web.
The Trust Problem
When you connect to a website over TLS, the server sends you a public key for encryption. But how do you know that public key actually belongs to the legitimate bank.com and not an attacker impersonating them? This is where digital certificates and Certificate Authorities (CAs) come in.
What is a Digital Certificate?
A digital certificate (typically X.509 format) is like a passport for a server. It contains:
- The server's public key
- The server's identity information (domain name, organization)
- An expiration date
- A digital signature from a trusted Certificate Authority
Think of it as a notarized document: the CA is the notary who vouches "Yes, this public key really belongs to bank.com."
How Certificate Authorities Work
A Certificate Authority is a trusted third party that validates server identities before issuing certificates. When bank.com wants a certificate:
- The bank generates a key pair and sends the public key + identity proof to a CA
- The CA verifies the bank actually controls the domain (via DNS records, email, or business documentation)
- The CA creates a certificate containing the bank's info and public key
- The CA signs this certificate with its own private key
Your browser comes pre-loaded with trusted CA public keys. During the TLS handshake, your browser verifies the CA's signature on the certificate, confirming the server's identity.
Chain of Trust
CAs themselves have certificates signed by higher-level CAs, forming a certificate chain back to a root CA that your browser inherently trusts.
Key Takeaway: Digital certificates bind public keys to identities, and Certificate Authorities act as trusted validators, enabling your browser to verify you're connecting to the real server, not an imposter.