Account

What new tool do you want?

Web & SEO

SSL Certificate Checker

Check any website's SSL/TLS certificate — valid or not, expiry date and days left, issuer, domains covered, TLS version and the full certificate chain.

How to use

  1. 1Enter a domain.
  2. 2See whether the certificate is valid, when it expires and what it covers.
  3. 3Renew before the countdown hits zero.

Frequently asked questions

What does “chain is incomplete” mean?

Your server isn't sending the intermediate certificate. Some browsers and most apps then reject the connection — add the intermediate (“full chain”) file in your server config.

How early should I renew?

At least 2–4 weeks before expiry. Let's Encrypt certificates last 90 days and are usually renewed automatically at 60.

Can I get expiry alerts?

Bookmark this page and re-check, or use your host's monitoring. We don't send emails.

Why 'incomplete chain' breaks some visitors but not others

A certificate chain runs from your domain's certificate up through one or more intermediate certificates to a root certificate that browsers trust natively — when a server is misconfigured to send only its own certificate and skip the intermediate, many modern desktop browsers paper over the gap because they've cached the missing intermediate from a previous visit elsewhere, while mobile browsers, older browsers and most non-browser apps (payment SDKs, API clients) have no such cache and reject the connection outright. That's why an incomplete chain can look fine when you check it yourself in Chrome but silently break for a meaningful share of actual visitors and integrations.

Worked example: SSL Certificate Checker

Checking a domain two days before its certificate expires shows a valid status with 'days left' counting down to near zero — worth renewing immediately rather than waiting, since the FAQ's 2-4 week buffer accounts for DNS propagation delays, certificate authority processing time, and the risk of an unexpected renewal failure. A Let's Encrypt certificate, by contrast, is issued for only 90 days and is typically configured to auto-renew at the 60-day mark — so seeing a Let's Encrypt cert with 70+ days remaining is completely normal, while seeing one with under 30 days remaining and no sign of renewal activity may indicate the auto-renewal process has quietly broken.

Why checking expiry here doesn't replace actual monitoring

This tool answers 'what's the certificate status right now, at the moment I check' — it has no way to alert you before a future expiry since, as the FAQ states plainly, it doesn't send emails or run on a schedule. A certificate that silently expires between manual checks causes an outage exactly like a server crash from your visitors' perspective (a browser security warning blocking the page entirely), which is why production sites generally need automated expiry monitoring from their host or a dedicated uptime service, with a tool like this reserved for spot-checks and troubleshooting.

What the names list and protocol row are actually telling you

The Names row lists every hostname the certificate's Subject Alternative Names field covers — for a single-domain cert that's often just the domain and its www. variant, but a wildcard or multi-domain cert can list dozens, which is exactly why the field truncates display after 30 entries. If the domain you typed isn't in that list, the certificate is still 'valid' in the sense of being correctly signed and unexpired, but browsers will show a hostname-mismatch warning anyway, because validity and matching are two separate checks. The Protocol row runs a second, independent check on top of that: any answer matching TLSv1 or TLSv1.1 gets an inline 'outdated — enable TLS 1.2+' note, since both versions are deprecated and increasingly blocked outright by modern browsers and PCI compliance rules, even on a certificate that is otherwise perfectly valid.

Self-signed certificates show up as a distinct failure, not a generic error

When a server presents a certificate it signed itself rather than one issued by a trusted certificate authority, the check reports it specifically as 'a self-signed certificate is in the chain' rather than a vague connection failure — useful because that message points to a completely different fix than an expired-certificate error would. A self-signed cert is normal and expected on an internal dev server or a home lab box, where there's no public domain to validate; it's a real problem the moment that same server is meant to be reached by ordinary visitors, since no mainstream browser will trust it without the visitor manually overriding a security warning first.

Related tools

More: Web & SEO