The TLS chain your server actually presents on the wire
Paste a hostname. Certglimpse opens a TLS connection, reads the certificate chain your server actually presents, and reports in plain language: the expiry date and days remaining, who issued it, every hostname the certificate covers, and whether the chain the server sends is complete.
Check a certificate
The point is the chain, not just the date
A certificate can be valid and the site still break, because the server sends the leaf without its intermediate certificate. Browsers on desktop paper over it from cache; mobile clients do not. That failure is invisible to anyone looking only at the expiry date — and it is the one people lose a weekend to.
Certglimpse reports what the wire actually carried, not what your browser cached.
What Certglimpse tells you
Expiry & days remaining
Is the certificate still valid? How many days until it expires?
Issuer
Who issued the certificate. Which CA signed it.
Subject Alternative Names (SANs)
Every hostname this certificate covers — not just the common name.
Chain completeness
How many certificates the server actually sent on the wire. A valid chain needs at least two: the leaf and its intermediate. Mobile browsers reject an incomplete chain.
One-shot, honest, no sign-up
- Checks only the hostname you type. No scanning, no enumeration.
- Reports what the server actually presented. If a field is absent, it says absent.
- No monitoring, no alerts, no re-checks. This tool answers when you ask it.
- Free. No account needed.