What this tool does
Connect to a server the way a browser would and read back the certificate it presents: who issued it, which names it covers, when it expires and whether the chain is complete.
How to use it
- Enter a hostname. Add :port for services other than HTTPS, such as mail.example.com:993.
- Read the warnings first: expiry, name mismatch and missing intermediates are the usual culprits.
- Open each certificate in the chain to see its details.
Questions and answers
Why does the site work in my browser but show an incomplete chain here?
Browsers cache intermediate certificates and can fetch missing ones. Most other clients, including curl, monitoring agents and mail servers, cannot. Configure the server to send the leaf plus every intermediate.
Which hosts and ports can I check?
Public hosts on ports that speak TLS from the first byte: 443, 465, 636, 853, 993, 995, 8443 and similar. Not supported: STARTTLS ports such as 25 and 587, servers that only accept TLS 1.3, and sites served through Cloudflare, because this checker runs on Cloudflare and cannot connect to Cloudflare's own addresses.
How is trust decided?
Each certificate's signature is verified against the next one in the chain, and the chain must end at a root in the Mozilla trust store. Revocation (OCSP and CRL) is not checked.