Website shows "Not secure": find the cause
Enter your domain. The tool checks what makes Chrome, Safari or Edge show "Not secure": the SSL certificate, the HTTPS redirect, content loaded over http and the TLS setup.
Why browsers say "Not secure"
- No SSL, or visitors land on http://: the address bar shows "Not secure".
- Expired certificate: a red "Your connection is not private" page (NET::ERR_CERT_DATE_INVALID).
- Wrong name or missing intermediate: e.g. a certificate for example.com used on www.example.com.
- Mixed content: an https page that still loads images, scripts or CSS over http://.
- Old TLS 1.0/1.1: modern browsers refuse or warn.
A red "Deceptive site ahead" page is Google Safe Browsing flagging the site, not an SSL problem: use the blacklist check.
Quick fixes
- Get a free certificate (Cloudflare, Let's Encrypt
certbot, or your host's free SSL) and turn on auto-renewal. - 301-redirect all http to https.
- Replace http:// links in posts and themes with https://.
- Turn on free email alerts to hear before the certificate expires.
Check your whole site, not just one thing
The free scan checks SSL, email spoofing, security headers, exposed sensitive files, outdated CMS and signs of hacking in one go, with plain-language fixes.
Free once you verify your domain: weekly re-scans and email alerts for new issues. PRO ($8/month): deep scan with 5,000+ known-vulnerability checks, deep re-scans up to 10 times a day and 5-minute uptime monitoring.
FAQ
I have SSL, why is it still "Not secure"?
Usually mixed content, no http-to-https redirect, or a certificate that doesn't match the hostname (missing www). The check above shows which.
Do free certificates trigger warnings?
No. Let's Encrypt and Cloudflare certificates are trusted by every browser.