Free SSL certificate checker

Check a website's SSL certificate

Good news first: checking a certificate is free, takes about ten seconds and touches nothing on your server. Enter a web address and you get a plain-English A to E grade, with the encryption findings explained alongside everything else visible about the site.

Run my free security checkabout 10 seconds, no account needed

The certificate is the part of website security people notice, because browsers are loud about it. An expired or mismatched certificate puts a full-page warning in front of every visitor, and most of them leave. It is also one of the easier problems to put right once you can see exactly what is wrong.

This page covers what the encryption part of our check reads, what each result means, and what to do about the findings that matter most.

What the certificate check reads

The encryption checks read exactly what a browser reads when it connects to your site. Nothing is installed, nothing is logged into, and your server sees an ordinary request.

  • Whether HTTPS is enforced, meaning a request to the plain http:// address is redirected rather than answered.
  • Certificate validity and expiry, including how many days are left before it lapses.
  • Who issued it, and whether that issuer chains to a root the major browsers trust.
  • Whether it matches the hostname you are actually visiting, which is where the www and non-www mix-up usually shows up.
  • Which TLS versions the server still accepts. TLS 1.0 and 1.1 have been retired by every major browser and should no longer be offered.
  • Mixed content, where a page served over HTTPS pulls in images or scripts over plain HTTP and quietly undoes part of the protection.
  • HSTS, the header that tells browsers never to try the insecure version again. That one is covered in more detail on the security headers check.

The certificate is one of roughly a dozen areas in the same scan, so you see it in context rather than on its own. How it works sets out the full list.

What each result means

Certificate findings range from something to tidy up this month to something that is costing you visitors right now. Roughly, in order of urgency:

FindingWhat it meansWhen to deal with it
Certificate has expiredEvery browser shows a full-page warning before any of your content. In practice almost nobody clicks through.Today
Certificate does not match the hostnameIt was issued for a different name. Usually a certificate covering example.co.uk but not www.example.co.uk, or a subdomain added later.Today
Self-signed or untrusted issuerThe encryption works, but no browser trusts it, so visitors still get the warning screen.Today
HTTPS is not enforcedThe site answers on http:// without redirecting. Anything typed on those pages travels in the clear.This week
TLS 1.0 or 1.1 still acceptedRetired protocols are still offered. Harmless to most visitors, but it fails PCI DSS and a lot of procurement questionnaires.This month
Mixed content on the pageAn HTTPS page is loading sub-resources over HTTP. Browsers block some of it and show the padlock differently.This month
Expires in under 30 daysNot a fault yet. It usually means renewal is manual, or automatic renewal has quietly stopped working.Before it lapses

Anything marked for today is a full-page browser warning, which is why it outweighs everything else in the grade.

Why certificates fail on their own

Most expired certificates belong to people who did nothing wrong. Certificates lapse on a schedule whether or not anyone is watching, and the usual causes are mundane.

  • Automatic renewal stopped silently. A renewal cron job, a hosting plugin or an ACME client fails, and nothing tells you until the certificate is gone.
  • The site moved. A migration to new hosting brings the files across but not the certificate, or brings it across without the renewal that kept it current.
  • A subdomain was added later. The original certificate covers the main domain only, so shop. or booking. or members. throws a warning the main site does not.
  • A proxy is terminating TLS somewhere unexpected. With Cloudflare in front, the certificate a visitor sees is not always the one on your origin server, and the two can disagree.
  • Nobody owns it. The developer who set it up moved on, and the renewal notice goes to an address that no longer exists.

Because of that last one, the useful thing is usually not a one-off check but a repeated one. Our optional weekly monitoring (£9.99 a month) re-runs the same scan and emails you when the grade changes or something new comes up, which for a certificate means you hear about it before your visitors do.

Fixing the common problems

In rough order of how often they come up:

  1. Renew or replace the certificate. Renewing an expired certificate walks through it. Free certificates from Let's Encrypt are issued for 90 days and are meant to be renewed automatically, so the fix is usually to repair the automation rather than to buy anything.
  2. Cover every hostname you actually use. If visitors reach you on both www and the bare domain, the certificate needs to cover both, and one should redirect to the other.
  3. Force HTTPS, then add HSTS. Redirect plain HTTP to HTTPS first and confirm nothing broke, then add the HSTS header. Doing it in that order matters, because HSTS is difficult to undo in a hurry.
  4. Clear up mixed content. Usually a handful of hard-coded http:// URLs in a theme, a stylesheet or the database. Fixing mixed content warnings covers finding them.
  5. Turn off the retired protocols. Disabling TLS 1.0 and 1.1 is a server or control-panel setting on most hosting, and takes a few minutes.

If the certificate is expired right now, that is the one thing worth doing before you read anything else on this page. Everything else can wait a day. That cannot.

What the check does not do

We would rather be clear about the limits than let you assume more than the scan can honestly give you.

  • It does not inspect your private key or anything else on your server. Everything read here is public.
  • It does not tell you whether the organisation behind a certificate is trustworthy. A valid certificate means the connection is encrypted, not that the site is honest. If that is the question you are asking, the website legit checker is the better starting point.
  • It does not audit your certificate management or renewal process, which is a conversation rather than a scan.
  • It does not check certificates on mail servers or other services, only the website on the address you give us.

Common questions

How do I check a website's SSL certificate?

Enter the address on the free security check and the certificate findings come back with the rest of the report in about ten seconds. You can also click the padlock in your browser and read the certificate details there, though that shows you validity rather than whether HTTPS is properly enforced across the site.

Does an SSL certificate make my website secure?

No, and this is the most common misunderstanding we see. A certificate encrypts traffic between the visitor and your server, which stops someone on the same network reading it. It does nothing about out-of-date software, exposed files, weak passwords or malware. Plenty of compromised sites have a perfectly valid certificate.

How long does an SSL certificate last?

Free certificates from Let's Encrypt last 90 days and are designed to renew automatically. Paid certificates have historically run for a year or more, though the industry is steadily shortening that. Either way, the practical question is not the length but whether renewal happens without anyone remembering to do it.

Do I need to pay for an SSL certificate?

For most small business websites, no. A free Let's Encrypt certificate provides exactly the same encryption as a paid one, and most UK hosting issues and renews them for you at no cost. Paid certificates add organisation validation and a warranty, which some businesses need for procurement reasons, but they are not stronger.

What happens when a certificate expires?

Browsers stop trusting the connection and show a full-page interstitial warning before any of your content loads. Visitors can technically click through, but very few do, and search engines and link previews treat the site as broken. Traffic usually falls off a cliff within hours.

Can I check a site I do not own?

Yes. The check only reads information the site already gives to anyone who asks for it, in the same way a browser does. You do not need to verify ownership, and the site owner is not notified.

How safe is your website?

A free A to E grade in about 10 seconds. No account needed.

Check my site