SSL certificates6 min read
How to check an SSL certificate's expiry date (browser, OpenSSL and monitoring)
By the RenewalRemind team
To check when a site's SSL certificate expires, click the padlock or site-settings icon in the address bar, open the certificate details and read "Expires on" (or "Valid until"). From a terminal, run openssl s_client against the site and print notAfter. To be warned before it expires, use a monitor that checks the certificate the site is actually serving — Let's Encrypt stopped sending expiry emails in June 2025.
Key takeaways
- Browser: site-settings icon → Connection is secure → Certificate is valid → Expires on.
- Terminal: openssl s_client … | openssl x509 -noout -enddate prints the exact expiry time (in GMT).
- Check the certificate the server is actually serving — a renewed certificate that was never installed still expires.
- Let's Encrypt ended its expiry reminder emails on 4 June 2025, so you need your own warning.
Every SSL/TLS certificate carries two dates: Not Before (valid from) and Not After (expires on). Browsers refuse the certificate outside those dates. Here is how to read them for any website, in a few seconds.
In Chrome or Edge
- Open the site and click the site-settings icon to the left of the address.
- Click Connection is secure, then Certificate is valid.
- On the General tab, read Expires on under Validity Period.
In Firefox
- Click the padlock in the address bar.
- Click Connection secure → More information → View Certificate.
- Read Not After under Validity.
In Safari (Mac)
- Click the padlock in the address bar, then Show Certificate.
- Expand Details and read Not Valid After.
With OpenSSL (any site, from a terminal)
This prints the exact expiry of the certificate the server is serving right now:
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null \
| openssl x509 -noout -enddateOutput looks like notAfter=Feb 14 23:59:59 2027 GMT. The -servername option matters: servers that host many sites pick the certificate by name, and without it you may see the wrong one.
To check it in a script, -checkend takes a number of seconds and fails if the certificate expires within that time:
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null \
| openssl x509 -noout -checkend $((14*24*3600)) \
&& echo "OK" || echo "Expires within 14 days"From a certificate file on your server
openssl x509 -in /etc/letsencrypt/live/example.com/cert.pem -noout -datesIf you use Certbot, sudo certbot certificates lists every certificate it manages with its expiry date and days left.
Let's Encrypt no longer emails you
Let's Encrypt used to email a warning when a certificate was close to expiring and hadn't been renewed. It ended that service on 4 June 2025, saying most users now renew automatically and recommending a monitoring service instead. If you relied on those emails, you currently have no warning at all when automatic renewal fails.
Common reasons auto-renewal fails:
- The Certbot timer or cron job stopped after a server migration or OS upgrade.
- HTTP validation is blocked by a redirect, firewall, CDN rule or a new
.htaccess. - DNS moved to a new provider and DNS validation credentials no longer work.
- The certificate renewed but the web server was never reloaded.
Get warned automatically
Checking certificates by hand doesn't scale, and certificates are getting shorter — down to 47 days by 2029. A monitor that connects to each site on a schedule, reads the live certificate and warns you a couple of weeks ahead catches every failure above. If you're already too late, see how to fix NET::ERR_CERT_DATE_INVALID.
Frequently asked questions
Does Let's Encrypt still send expiry emails?
No. Let's Encrypt stopped sending certificate expiration notification emails on 4 June 2025 and recommends automated renewal plus a monitoring service.
What time zone is the SSL expiry date in?
Certificate dates are stored in UTC (GMT). OpenSSL prints them in GMT; browsers convert them to your local time.
My certificate auto-renews — do I still need to check it?
Yes. Auto-renewal fails silently when a cron job or timer stops, DNS or firewall changes break validation, or the web server isn't reloaded and keeps serving the old certificate.