- Home
- Technical and performance
- SSL Certificate Checker
SSL Certificate Checker
Check that your certificate is valid, complete, and not about to expire quietly.
A real TLS connection is opened to the host and the certificate it actually presents is read — not a cached record from a database. Chain completeness is verified as a browser would verify it. No usage limit.
What this tool is for
A certificate proves that the site answering is genuinely the one whose address you typed, and it encrypts everything in between. Without a valid one, browsers no longer show a discreet warning: they interpose a full-screen barrier that most visitors will never click through.
The dangerous failure is not a certificate that is wrong — it is one that is quietly about to expire. Automatic renewal works until the day it does not, and nothing announces the breakage. The site stays perfectly normal right up to the expiry date, then goes dark for everyone at once.
This tool reads what your server actually presents. Expiry date, issuer, chain completeness, and which hostnames are covered — the last one catching the classic case of a certificate valid for www and invalid for the bare domain.
How to read your results
Days remaining is the number to act on. Below thirty is a warning regardless of what the automation claims, because thirty days is exactly when Let's Encrypt should already have renewed. A certificate sitting at fifteen days is not "still valid" — it is a renewal that has failed silently.
The covered names must include every hostname visitors actually reach.
A certificate for www.example.com produces a warning on
example.com, and the redirect from one to the other happens after the TLS
handshake — so the warning appears first.
The chain of trust must be complete. An incomplete chain is the trickiest failure to diagnose because desktop browsers often repair it silently while mobile browsers and API clients refuse. "It works on my machine" is the signature of this problem.
The issuer is informational for most sites. Let's Encrypt, ZeroSSL and commercial authorities all produce certificates browsers trust identically. What matters is that renewal is automated and proven, not who signed it.
The most common mistakes
Assuming automatic renewal works because it worked last time. Renewal breaks for mundane reasons: a changed DNS record, a validation directory that became unreachable, a hosting migration. Nothing notifies you. Checking the remaining days occasionally is the only reliable signal.
Covering only one form of the domain. Visitors, old links and email clients use both. Both must be in the certificate, and both must be reachable — check the redirect chain at the same time.
Trusting a green padlock on your own desktop. Your browser may be completing an incomplete chain for you, and it may have cached an intermediate weeks ago. A server-side check is the only way to see what a first-time mobile visitor sees.
Publishing HSTS before the certificate is reliable. HSTS instructs browsers to refuse plain HTTP for its full duration. Combined with an expired certificate, it produces a site nobody can reach by any means until the max-age runs out.
Buying an expensive certificate to fix a warning. Warnings almost never come from the certificate being too cheap. They come from expiry, a missing hostname, or a broken chain — none of which more money resolves.
Related tools
- Security Headers Checker Audit the five HTTP headers that protect your visitors
- Redirect Checker Follow the full redirect chain of a URL, hop by hop
- DNS Lookup A, MX, TXT, NS records and full DNS configuration
- Whois Lookup Registration, expiry and ownership details of a domain name
Frequently asked questions
How long before expiry should I worry?
Thirty days. Let's Encrypt certificates are automatically renewed at that point, so a certificate with fewer than thirty days left is telling you the automation has failed. Waiting to find out is how sites go dark: on expiry day every browser shows a full-screen warning and traffic falls to nothing.
What is an incomplete certificate chain?
Your certificate is signed by an intermediate authority, which is signed by a root the browser already trusts. The server must send the intermediate along with your certificate. Many desktop browsers paper over a missing intermediate by fetching it themselves; mobile browsers and API clients often do not — which is why the classic symptom is a site that works on your laptop and fails on a phone.
Is a paid certificate more secure than a free one?
The encryption is identical. A Let's Encrypt certificate and a certificate costing three hundred a year protect the connection exactly the same way. What you buy is organisational validation, warranty, and support. For most sites the free certificate is the correct engineering choice, not a compromise.
Does HTTPS help SEO?
Google confirmed HTTPS as a lightweight ranking signal in 2014, and it has been the assumed baseline for years. The real effect is not the signal — it is that browsers mark HTTP pages as insecure, which destroys conversion long before rankings become the issue.
Why does my certificate cover www but not the bare domain?
Because it was issued for one hostname only. A certificate covers exactly the names listed in it. If example.com and www.example.com both need to work, both must appear — either as separate entries or through a wildcard. This is one of the most common causes of intermittent warnings.
What is HSTS preloading?
A list built into browsers of domains that must only ever be reached over HTTPS, before any request is made. It removes the very first redirect. It is also close to irreversible: removal from the list takes months to reach users. Only preload a domain that will use HTTPS permanently.