SSL Checker
Type your website address. The checker connects the way Chrome does, reads the certificate, counts the days it has left and tests the four other things that make a browser call a site Not secure.
Issued to
Every site I build gets a certificate that covers both the www and the bare address, plus the redirect, before launch. Book a free 20-minute strategy call if your result needs work.
36 Toronto web design studios, checked on November 17, 2026
I ran this tool on the studios from my GTA website price survey. Every certificate was valid: 22 came from Let's Encrypt and 14 from Google Trust Services, all of them 90-day certificates that renew themselves. The problems were all around the certificate.
The three broken twins are the ones to fear, because the owner never sees them. One had a www certificate that ran out, one served a certificate for a different name, and one refused the secure connection outright. I opened all three in curl on my own computer and got the same three errors.
Why a valid certificate can still show Not secure
Chrome judges the page in front of it, not the certificate alone. Four things on this checker have nothing to do with buying or renewing a certificate:
- Both halves of your address need the certificate. People type
www.yourbusiness.comandyourbusiness.com, and the browser checks whichever one they typed. - The plain http address has to send people on to https. Old links, printed flyers and business cards often say http://, and without the redirect the page opens unprotected.
- Every picture, script and form on the page has to use https. One http:// address takes the padlock away even when the certificate is perfect.
- The HSTS header tells the browser to skip http on later visits. It is optional, and half the studios above leave it out.
I logged what the engine inside Chrome shows for each of these on 14 broken test pages, in what each Not secure warning means.
Certificates keep getting shorter
A certificate that renews itself, like every one in the survey above, is not affected. One that someone buys and installs by hand now needs that person twice a year, and eight times a year from 2029. The days-left line in the result shows which kind you have: a free automatic certificate is replaced about 30 days before the end, so a number much lower than that means the renewal is not running. The full timeline is in SSL certificates now last 200 days.
Questions about the SSL checker
Does the checker change anything on my site?
No. It connects to the site and reads the home page the way a browser does, then shows what it saw. Nothing is installed or stored, apart from a count of checks from your connection, which allows 30 an hour.
Everything passes here. Why does Chrome still say Not secure?
The checker reads the page you typed, usually the home page. The warning may come from another page that loads an http:// picture or posts a form to an http:// address. Open that page, type its full address here and check again.
Does it check whether the certificate was revoked?
No. It checks the name, the dates and the path back to an authority that browsers trust. Revocation lists are a separate system that this checker does not read.
Do I need HSTS?
It is a good extra once every page works on https, not a requirement. Set it with a short max-age first, then raise it to a year. Turn it on too early and any page that still breaks on https becomes impossible to reach until the time runs out.
Does https help my Google ranking?
Google has used https as a ranking signal since 2014 and called it a lightweight one. The bigger cost of a broken certificate is the full-page warning a visitor sees before your site, with a button that takes them back.
Check the rest of the site too
The free website audit runs the certificate checks together with speed, SEO, email and accessibility in one report, and the SPF, DKIM and DMARC checker looks after the email side of the same domain.