Skip to content
search-engine-optimizedby Netsolution
  1. Home
  2. Technical and performance
  3. SSL Certificate Checker

SSL Certificate Checker

Check your certificate before your visitors run into a security warning.

A direct TLS connection to the server and a reading of the certificate presented, intermediates included. Nothing is stored, and there is no usage limit.

What this tool is for

A certificate that expires gives no warning. One morning, every visitor gets a full-page notice telling them the connection is not secure. Almost all of them turn back, and you learn about it only from the drop in traffic.

That is not the only possible fault. An incomplete certificate chain produces a site that works perfectly on your computer and shows an error on certain phones — invisible, therefore, to your own test. A certificate that does not cover the www version breaks half the accesses.

This tool opens a real TLS connection and checks the four points that actually fail in production: validity in time, completeness of the chain, domains covered, and protocol versions accepted.

Careful if you have enabled HSTS: an expiry then becomes unrecoverable on the visitor’s side. The browser refuses the connection and offers no way to proceed anyway. The link between the two settings is worth knowing.

How to read the results

The expiry date is the most watched and the simplest point. Below thirty days, check that automatic renewal genuinely works — it fails regularly without raising an alert.

The certificate chain has to be complete from your domain’s certificate up to a recognised root authority. A missing intermediate produces an intermittent error depending on the device, and is particularly hard to diagnose.

The domains covered list every name validated by this certificate. Check that both the www and non-www versions appear, along with the active subdomains.

The TLS versions accepted reveal the security posture. TLS 1.3 ideally, TLS 1.2 at minimum. The presence of TLS 1.0 or 1.1 signals a configuration nobody has revisited for years.

The issuing authority confirms the provenance. An unexpected issuer on your own domain deserves an immediate check.

Common mistakes

Trusting the browser padlock. It says the connection is encrypted, nothing more. A certificate expiring in two days, an incomplete chain or an obsolete protocol all show the same reassuring padlock.

Believing automation is infallible. Automatic renewal fails for many reasons: a firewall rule, a misplaced redirect, a quota reached. It fails silently, and nobody notices before the expiry.

Testing only from your own computer. Desktop systems often complete an incomplete chain themselves, which phones do less. The fault stays invisible to anyone testing a single device.

Forgetting the subdomains. The main domain is watched; the subdomain created for a one-off campaign expires unnoticed and ends up showing a security warning.

Leaving resources on HTTP inside an HTTPS page. An image or a script loaded in the clear triggers a mixed-content warning and may be blocked. Check the page source for those calls.

Going further

Frequently asked questions

Does an expired certificate cost rankings?

Not immediately, but the effect is worse than losing positions. Browsers display a full-page warning that turns almost every visitor away, and Google eventually becomes unable to crawl the site. A few days of expiry are enough to drop traffic to almost nothing.

What is an incomplete certificate chain?

A certificate is validated by climbing to a root authority, through intermediate certificates the server has to supply. If one is missing, some browsers fill the gap themselves and others do not. The classic symptom is a site that works on a desktop and shows an error on mobile.

Is a free certificate as good as a paid one?

Technically yes: the encryption is identical. The difference is the level of validation. A free certificate attests that you control the domain; an extended validation certificate attests to the company’s legal identity. Browsers have not displayed that distinction since 2019, which has greatly reduced its value.

Should older TLS versions be disabled?

Yes. TLS 1.0 and 1.1 have been deprecated since 2020 and are rejected by every current browser. Leaving them on serves only obsolete clients while keeping known weaknesses alive. TLS 1.2 as a minimum, TLS 1.3 for preference.

Does my certificate cover subdomains?

Only if it is a wildcard, declared for *.example.com, or if it explicitly lists each subdomain. A certificate issued for example.com does not even cover www.example.com unless expressly stated. That is a frequent cause of errors after a new subdomain goes live.

How often should I watch for expiry?

If renewal is automated, a monthly check is enough — automation sometimes fails silently. If it is manual, set an alert thirty days before the deadline. The most frequent cause of expiry is not forgetfulness but an out-of-date payment method at the provider.