Security · interactive
Certificates and the chain of trust
Your browser trusts a few hundred root authorities. A site's certificate is trusted only if it links back to one of them through signatures, is in date, and names the site you asked for. Break one link and you get the red warning page.
https://shop.example.com
ISRG Root X1root
issued by ISRG Root X1 · valid until 2035-06-04
already in the browser's trust store
↓ signs
R11 (intermediate)intermediate
issued by ISRG Root X1 · valid until 2027-03-12
sent by the server
↓ signs
shop.example.comleaf
issued by R11 (intermediate) · valid until 2027-03-01
sent by the server
- ✓ Chains to a root in the trust store
Leaf ← R11 ← ISRG Root X1, which ships with the OS/browser.
- ✓ Each signature verifies
Each certificate is signed by the private key of the one above it.
- ✓ Within validity dates
Today is inside every certificate's validity window.
- ✓ Name matches shop.example.com
Listed in the Subject Alternative Name.
Connection is secure
Every link checks out: the leaf is signed by R11, R11 by a root the browser already trusts, dates are fine and the name matches.
Scenario
Step 1 of 4 · read left to right
In production
Tools and technologies
Every HTTPS connection validates a certificate chain.
Not tied to one language — use these names when you search docs or design a system.