Expiry
Days left on the certificate the server actually presents right now.
Monitor
Protect
Manage
By role
Security
Renewals
Monitoring
Free tool · No signup
Connect to a site and read its TLS certificate: who issued it, when it expires, which names it covers and whether the chain would be trusted.
No domain handy?
Lookups run live and are not stored.
Every result is pulled live, so you see the state of the domain right now.
Days left on the certificate the server actually presents right now.
Whether a browser would accept the chain, and whether the name matches.
Every hostname on the certificate, so a missing subdomain is easy to spot.
| Result | What visitors see | Fix |
|---|---|---|
| Expired | A full-page browser warning | Renew and install the new certificate |
| Name mismatch | A warning that the certificate is for another site | Reissue with the right hostnames |
| Untrusted chain | A warning, or failures in apps and APIs | Serve the full chain including intermediates |
| Under 14 days left | Nothing yet | Check that auto-renewal actually runs |
| Valid and trusted | The padlock | Keep monitoring the expiry |
Use the exact name visitors use, for example www.example.com.
It combines expiry, name match and chain trust into one line.
Short lifetimes mean manual renewal is the usual cause of expiry outages.
Enter the site above. The checker connects on port 443, reads the certificate and shows the date it expires and the days remaining.
Usually the server is not sending an intermediate certificate, or the certificate is self-signed. Browsers may fetch missing intermediates; many apps do not.
Only if the subdomain is listed or matched by a wildcard. The tool lists every name on the certificate.
The browser industry has agreed to reduce maximum certificate lifetimes over the next few years, which makes automated renewal necessary.
Aepto alerts you on SSL expiry for the sites you monitor, which matters more as certificate lifetimes keep shrinking.
