Quick access

Saved in this browser. Sign in to keep it on all your devices.

SSL Checker

Check whether a site’s HTTPS certificate is trusted by browsers, which names it covers, how many days are left, its full chain, and which TLS version the server uses.

You can paste a full web address or an email address; we use just the domain.

Version 1.1 Updated What's new

Release notes

  1. v1.1 Latest
    • Added an in-depth guide below the tool, written from what the tool actually does.

About the SSL Checker

The SSL checker connects to a website and reads its TLS certificate, showing the issuer, the domains it covers, the expiry date, and whether browsers will trust it.

How to use it

  1. 1 Enter a domain.
  2. 2 Run the check.
  3. 3 Review the checks, days until expiry, covered names, and the certificate chain.

Frequently asked questions

How long are SSL certificates valid?

Public certificates issued since March 2026 last at most 200 days. The limit drops to 100 days in March 2027 and 47 days in March 2029, so automatic renewal is becoming essential.

Why does my site show "Not secure"?

The certificate may have expired, not cover that exact domain (such as www), or be missing an intermediate certificate.

Is SSL the same as TLS?

TLS replaced SSL years ago, but people still call the certificates "SSL certificates".

What does "missing intermediate" mean?

The server sends its own certificate but not the intermediate that links it to a trusted root. Some browsers fill the gap, but phones, apps, and APIs often fail. Install the full chain file from your certificate provider.

How the check works

The tool opens a real TLS connection to port 443 of the first address the domain resolves to, and sends the host name the way a browser does. It tries first with full verification. If that fails, it reconnects without verification so that it can still read the broken certificate and explain the fault.

Results are cached for 2 minutes, so wait briefly after installing a new certificate. A site behind a CDN or several servers can answer differently from one address to the next, and private addresses are refused.

Common reasons for a failed check

  • Expired: the renewal job stopped working, or the new certificate was issued but the web server was never reloaded.
  • Wrong name: the certificate lists other domains, which often happens on shared hosting or after a domain move.
  • Self-signed: no certificate authority vouches for it. Fine on a test server, but visitors will see a warning.
  • Missing intermediate: the server sends only its own certificate. Point it at the full chain file instead.
  • Outdated TLS: versions before 1.2 are flagged, because current browsers refuse them.
  • Weak key or signature: RSA keys under 2,048 bits and SHA-1 or MD5 signatures are flagged.

The expiry check warns under 30 days and fails under 14. If you use automatic renewal and see a certificate inside that window, look at the renewal logs.

How wildcards and www are matched

A wildcard covers exactly one level. *.example.com covers www.example.com and shop.example.com, but not example.com itself and not a.b.example.com. For that reason the report also tests the other form of your address, with or without www, since people type both.

Shorter certificate lifetimes

Browser and certificate authority rules are cutting the maximum life of public certificates: 200 days from March 2026, 100 days from March 2027 and 47 days from March 2029. Renewing by hand once a year is no longer workable. Set up an ACME client such as Certbot, or use your host’s automatic certificates, then test the renewal before you depend on it.