How the check works
The tool opens a real TLS connection to port 443 of the first address the domain resolves to, and sends the host name the way a browser does. It tries first with full verification. If that fails, it reconnects without verification so that it can still read the broken certificate and explain the fault.
Results are cached for 2 minutes, so wait briefly after installing a new certificate. A site behind a CDN or several servers can answer differently from one address to the next, and private addresses are refused.
Common reasons for a failed check
- Expired: the renewal job stopped working, or the new certificate was issued but the web server was never reloaded.
- Wrong name: the certificate lists other domains, which often happens on shared hosting or after a domain move.
- Self-signed: no certificate authority vouches for it. Fine on a test server, but visitors will see a warning.
- Missing intermediate: the server sends only its own certificate. Point it at the full chain file instead.
- Outdated TLS: versions before 1.2 are flagged, because current browsers refuse them.
- Weak key or signature: RSA keys under 2,048 bits and SHA-1 or MD5 signatures are flagged.
The expiry check warns under 30 days and fails under 14. If you use automatic renewal and see a certificate inside that window, look at the renewal logs.
How wildcards and www are matched
A wildcard covers exactly one level. *.example.com covers www.example.com and shop.example.com, but not example.com itself and not a.b.example.com. For that reason the report also tests the other form of your address, with or without www, since people type both.
Shorter certificate lifetimes
Browser and certificate authority rules are cutting the maximum life of public certificates: 200 days from March 2026, 100 days from March 2027 and 47 days from March 2029. Renewing by hand once a year is no longer workable. Set up an ACME client such as Certbot, or use your host’s automatic certificates, then test the renewal before you depend on it.