TLS certificate chain reader
Read five certificate chains the way a client does: hostname, dates, issuer links, and trust. Find the expired leaf, the missing intermediate, and the bad wildcard.
What you’re looking at
Read five certificate chains the way a client does: hostname, dates, issuer links, and trust. Find the expired leaf, the missing intermediate, and the bad wildcard.
Your goal: Read five certificate chains the way a browser does and say exactly why each broken one fails.
- Host
- the five server names on the left. Click one to load the certificates it sent.
- Show openssl s_client output
- a switch that shows the same chain as the openssl command line tool prints it.
- Chain panel
- the right side. One card per certificate with Subject (who it is for), Issuer (who signed it), SAN (the names it covers), and Valid dates.
- Client checks
- the list below the cards: name match, dates, issuer links, and trusted root, each pass or fail.
- Walkthrough
- the numbered path beside the workbench (below it on a phone). Each step says what to do and what you should see. Hints open one at a time.
Words you will meet
- TLS
- Transport Layer Security, the encryption behind HTTPS
- CA
- certificate authority, who signs TLS certificates
Start with step 1 in the walkthrough. Every step says what to do and what you should see. The whole thing takes about 2 min to talk through.
Briefing
Five internal hosts answered a TLS handshake. For each one, read the certificates the server sent and run the checks a client makes: does the name match, are the dates valid, does each issuer link to the next certificate, and does the chain end at a trusted root?
The lab clock is 2026-03-14T09:00:00Z, and the client trusts one root: CN=HackBlue Lab Root R1, O=HackBlue Lab Trust.
Host
View
- depth 0
- Subject
CN=www.contoso.example- Issuer
CN=HackBlue Lab Issuing CA 2, O=HackBlue Lab Trust- SAN
www.contoso.example, contoso.example- Valid
- 2026-01-10 to 2026-04-10
- depth 1
- Subject
CN=HackBlue Lab Issuing CA 2, O=HackBlue Lab Trust- Issuer
CN=HackBlue Lab Root R1, O=HackBlue Lab Trust- Valid
- 2024-06-01 to 2029-06-01
Client checks
- passName matches the hostwww.contoso.example vs www.contoso.example, contoso.example
- passEvery certificate is within its validity dateschecked at 2026-03-14T09:00:00Z
- passEach issuer matches the next subject2 certificate(s) sent
- passChain ends at a trusted rootissued by HackBlue Lab Root R1, in the trust store
Verified. The client completes the handshake.
The whole walkthrough
Every step in order, written to be read aloud: 299 words, about 2 min. It gives away every answer, so try the steps first.