SSL certificate checker
See who issued the certificate, when it expires, how many days are left, and whether the hostname you entered is listed on it.
The check runs from this server. Only public http and https sites on ports 80 and 443 are allowed.
Checking…
How to read the result
A TLS certificate binds a hostname to a public key and has a limited lifetime. This check looks at the leaf certificate presented on port 443 and reports three things that commonly cause browser warnings:
- Expiry. After the not-after date, the certificate is invalid. Let’s Encrypt certificates are valid for 90 days; many commercial CAs issue certificates for up to about a year. This tool flags a certificate as “expires soon” when 21 days or fewer remain — that threshold is only for the warning label, not a rule issued by a CA.
- Hostname match. The name you requested must appear in the certificate’s Subject Alternative Name list (or, if there is no SAN, the common name). A certificate for www.example.com does not automatically cover example.com. A wildcard such as *.example.com covers one label only (app.example.com, not a.b.example.com, and not example.com itself).
- Issuer. The issuer field is the organisation named on the leaf certificate. This tool does not fully validate the chain the way a browser does; a trusted issuer name is not a complete substitute for path validation.
The result is the state from this server at the moment you run the check. It will not email you when the certificate is close to expiry unless you check again — scheduled SSL monitoring is what uptime tools are for.