SSL check

Check a site's certificate, chain, expiry and TLS versions, for the domain and its www name.

A domain or URL; port 443 is always checked.

A few free checks a day without an account. Sign in to use your credits.

Check many at once

Bulk checks aren't unlocked yet

Bulk checks unlock after your first credit purchase or plan. Single checks work as usual.

Sign up free

What the SSL check tells you

Every site that loads over HTTPS shows browsers a certificate: a signed file that says which names the site may use and which certificate authority vouched for it. When the certificate has expired, covers the wrong name or can't be traced back to an authority the browser trusts, visitors see a full-page security warning instead of your site, and most of them leave.

The SSL check connects to your site the way a browser does, collects the certificate and everything the server sends with it, and checks it all on our side. You get one card per name, a plain verdict, a grade, and the exact fix for anything that's wrong.

What we check

For the domain you enter, and for its www name when you enter a domain without a subdomain, we look at:

  • Trust. Whether the certificate leads, step by step, to a root in the Mozilla root store, the same list Firefox and most Linux systems trust. We verify every signature in the chain ourselves.
  • Names. Whether the certificate covers the exact name visitors typed. A wildcard such as *.example.com covers www.example.com but not example.com itself.
  • Dates. When the certificate started and when it ends, with the number of days left. We warn a month before expiry and raise it to a failure two weeks before.
  • The chain as sent. Each certificate the server sends, in order, so you can see whether the intermediate certificate is missing, the order is wrong or a root is sent for nothing. Every certificate comes with its PEM text to copy.
  • Key and signature. RSA keys shorter than 2048 bits, elliptic-curve keys under 256 bits and SHA-1 signatures are all reported, because browsers reject them.
  • Protocols. Which TLS versions the server accepts. TLS 1.3 should be on; TLS 1.0 and 1.1 should be off. We also test whether the server still accepts key exchange without forward secrecy.
  • Extras. OCSP stapling and embedded transparency proofs (SCTs), shown as information.

How the grade works

The grade starts at 100 and loses points for each problem, weighted by how much it hurts visitors. An expired, revoked or untrusted certificate costs the most, because browsers block the page outright. A missing intermediate costs less, because some browsers work around it. Old protocol versions and a missing TLS 1.3 cost a little: they don't stop anyone visiting today, but they're worth fixing. Information findings, such as a www name with no address, cost nothing. A is 90 and up; below 50 is F.

Reading the result

Each card starts with a one-line verdict, such as "Trusted, 62 days left". Under it you'll find who issued the certificate, when it expires, the names it covers, the key, the connection we got, and the address and port we checked. The chain section lists the certificates in the order the server sent them; a healthy chain is your certificate first, then one or two intermediates. The table at the bottom shows each TLS version as accepted, not offered, or not tested. "Not tested" means the server took too long for us to run the extra handshakes; it is never counted against you.

If a name has no address at all, we say so as information rather than failing it: plenty of domains don't use www. If the name points to a private network address we don't connect and say why. A name with only IPv6 addresses is checked over IPv6 while our IPv6 connection is on, and marked as not checked while it is off.

What we never do

We only complete TLS handshakes. We never send a web request, never follow redirects and never fetch anything from your site. We also never ask certificate authorities, revocation servers or transparency logs about your certificate: each of those requests would tell an outside company which site is being checked. That is why revocation is only judged from a stapled answer your server sends, and why a missing intermediate is reported rather than quietly downloaded.

Common fixes

Most problems come down to the certificate files on the server. An expired certificate needs renewing, and usually means automatic renewal has stopped. A name mismatch means the certificate was issued for a different set of names; issue one that lists every name you use. A missing intermediate means the server is configured with the certificate alone instead of the full chain file your authority provides. Each finding in the result links to a step-by-step guide.

Questions

Why does the check look at www as well?
Visitors type both. If you check example.com we also check www.example.com, because a certificate that covers one name and not the other is one of the most common causes of security warnings. A subdomain such as shop.example.com is checked on its own.
My browser shows the padlock but you report a missing intermediate. Who is right?
Both. Many desktop browsers fetch a missing intermediate certificate themselves or remember it from another site, so they cope. Phones, apps, payment systems and command-line tools usually don't, so they fail. Sending the full chain fixes it for everyone.
Do you check whether the certificate has been revoked?
Only when the server staples a revocation answer to the handshake. We never contact certificate authorities, revocation lists or transparency logs ourselves, because each request would tell a third party which site is being checked.
Which port do you check?
Port 443, the standard HTTPS port, always. The check can't test mail servers or services on other ports.
How much does a check cost?
In the browser you get a few free checks a day without an account. Through the API or MCP a check costs 1 credit, and a cached answer costs the same. Answers are cached for up to an hour, never past the certificate's expiry. Checks that fail on our side are free.