SSL certificate checker and expiry check
What we look at
- Validity: whether browsers trust the certificate chain, and whether it's within its valid dates.
- Days to expiry: how long you have before it needs renewing. We flag anything under 30 days, and treat under 7 as urgent.
- Hostname match: whether the certificate actually covers the domain you typed, including
wwwif that's where visitors land. - Issuer: who issued it, such as Let's Encrypt or a commercial authority.
- Protocol: which version of TLS your server negotiates. TLS 1.2 and 1.3 are current; anything older should be switched off.
- Redirect: whether
http://sends visitors to the encryptedhttps://version.
We also look up your DNS A and AAAA records, because a certificate check needs to know which server it is talking to, and whether a CAA record restricts who can issue certificates for your domain.
Healthy versus needs attention
[tls] TLSv1.3 · cert valid · expires in 212d · issuer: Let's Encrypt pass
[http] :80 → :443 redirect pass// hacker view
[tls] TLSv1.2 · cert valid · expires in 5d fail
// plain english
Your padlock stops working in five days. After that, visitors see a warning instead of your site. Renew the certificate now, and switch on automatic renewal if your host offers it.
A hostname mismatch usually means the certificate was issued for a different name, often example.com without www, or the other way round. A chain error usually means the server isn't sending an intermediate certificate. Both are configuration fixes rather than new purchases.
What this check does not do
It makes one TLS connection, one home page request and one http:// request, plus a few DNS lookups. It doesn't test every cipher your server supports, doesn't check other subdomains, and doesn't probe for weaknesses. For a full cipher-by-cipher review, a deeper authorised scan is the right tool, and we only run those once you've proved ownership and given written permission.
Fixing the common certificate problems
- Expiring soon: renew it, then turn on automatic renewal. Most hosts and free authorities support this.
- Wrong name: reissue the certificate to include every name visitors use, usually both the bare domain and
www. - Old TLS versions: disable TLS 1.0 and 1.1 in your server or hosting settings.
- No redirect: add a permanent (301) redirect from
http://tohttps://, then consider HSTS.
Common questions
My certificate renews automatically. Do I still need to check it?
It's worth a glance now and then. Automatic renewal is reliable when it works, but it fails quietly more often than people expect: a domain moves to a new host, a DNS change breaks the validation step, or a payment card on the hosting account expires. Nobody notices until visitors see a full-page warning. Checking every month or two, or letting monitoring do it for you, catches a failed renewal while there are still weeks to spare rather than hours.
Do I need a paid certificate, or is a free one good enough?
For almost every small business website, a free certificate from an authority such as Let's Encrypt gives exactly the same encryption and the same padlock as a paid one. Paid certificates can make sense for specific needs, such as a warranty your contract requires or a particular validation type, but they don't make the connection stronger.
What's the difference between SSL and TLS?
TLS is the modern version of SSL. People still say “SSL certificate” out of habit, but the connection itself uses TLS. See our TLS glossary entry.
How do I check when my SSL certificate expires?
Type your domain above: the result shows the expiry date as days remaining, and flags anything under 30 days. You can also click the padlock in your browser and open the certificate details. To be told before it lapses, see website security monitoring.
Does a valid padlock mean my site is safe?
It means the connection is encrypted and goes to the right server. It says nothing about the software running your site. That's why the full check looks at more than the certificate.
Why does my certificate show as valid in my browser but not here?
Browsers sometimes fill in a missing intermediate certificate from their cache. Our check sees what a fresh visitor sees, so a chain problem shows up here first.
// related
// terms on this page
Never be surprised by an expired certificate
When we look after your site, we keep an eye on your certificate and tell you before it lapses, along with anything else that changes. It starts with a short call.