The TLS certificate chain, read directly from the wire

Paste a hostname. Tlsscope opens a TLS connection, reads the certificate chain the server sends on the wire, and reports the expiry date, issuer, covered hostnames, and whether every intermediate was transmitted.

This is not a cached or guessed value. It is what the server actually sent.

Why the chain matters

A certificate can be valid and the site still break, because the server sends the leaf without its intermediate certificate. Desktop browsers cache the missing intermediate from previous visits and paper over the gap. Mobile clients do not. That failure is invisible to anyone checking only the expiry date, and it is the one people lose a weekend to.

Tlsscope reports whether the server sent a complete chain — every intermediate needed to build trust from the leaf to a recognised root — or omitted certificates that will cause some clients to reject the connection.

What the report includes

Expiry date and days remaining
Issuer organisation and common name
All subject alternative names the certificate covers
Certificate chain depth and completeness assessment
Serial number and SHA-1 fingerprint
Check a certificate now See plans
One hostname at a time. Port 443 only. Tlsscope answers when you ask — it does not send alerts, reminders, or scheduled re-checks. No accounts, no stored data. Hosts behind Cloudflare are reachable (the inspection runs from a real machine, not the edge).