Digital Certificates Fundamentals
You'll learn what X.509 certificates contain and how they establish identity in TLS connections.
What Is a Digital Certificate?
A digital certificate is like a passport for websites and servers. Just as a passport proves your identity with a photo, signature, and government seal, a digital certificate proves a server's identity using cryptographic information and a trusted authority's signature.
When you connect to https://example.com, how do you know you're really talking to Example Inc.'s server and not an imposter? Digital certificates provide that proof during the TLS handshake we learned about previously.
X.509 Certificate Contents
The X.509 standard defines what goes into a digital certificate. Key components include:
- Subject: Who owns this certificate (e.g.,
example.com) - Issuer: Which Certificate Authority (CA) verified and signed it
- Public Key: The server's public key for asymmetric encryption
- Validity Period: Start and expiration dates (typically 1-2 years)
- Digital Signature: The CA's cryptographic signature proving authenticity
- Serial Number: Unique identifier for tracking
- Extensions: Additional information like allowed domain names
How Certificates Establish Identity in TLS
During the TLS handshake, the server sends its certificate to the client. Your browser then:
- Checks if the certificate is signed by a trusted CA (from its pre-installed CA list)
- Verifies the signature hasn't been tampered with
- Confirms the certificate hasn't expired
- Ensures the domain name matches the one you're visiting
If all checks pass, your browser trusts it's talking to the real server and proceeds with symmetric key exchange using the certificate's public key.
Key Takeaway: X.509 digital certificates act as cryptographically-signed identity documents that prove a server's authenticity during TLS connections, containing the server's public key, identity information, and a trusted Certificate Authority's signature.