What the checker looks at
- Expiry: how many days are left. Let's Encrypt certificates last 90 days and renew automatically; a warning here usually means renewal is failing.
- Trust: whether browsers accept the certificate. Self-signed certificates and a missing intermediate certificate are the usual problems.
- Names: whether the certificate covers the exact name you entered. A certificate for
example.comdoes not covershop.example.comunless it lists it or uses*.example.com. - Connection: the TLS version (1.2 or 1.3 today) and the key type.
You can also check mail servers on ports 465, 993 and 995.
Fixing common problems
- Expired: renew it. With Certbot:
sudo certbot renew, then check the timer withsystemctl list-timers. - Missing intermediate: install the full chain (
fullchain.pem), not only the certificate. - Wrong name: issue a certificate that includes every name visitors use, such as both
example.comandwww.example.com.
Frequently asked questions
How do I check when an SSL certificate expires?
Enter the domain above. The checker shows the exact expiry date and the days left, and warns when fewer than three weeks remain.
Why does my site work in one browser but not another?
Usually a missing intermediate certificate. Some browsers fill the gap from cache, others don't. Serve the full chain.
Can I check a server on my local network?
No. For safety the checker only connects to public internet addresses.
Sources
The rules and figures in this tool come from these official sources, last checked November 12, 2026.
- RFC 8446: TLS 1.3 rfc-editor.org
- Mozilla: server side TLS guidelines wiki.mozilla.org