Why Does My Site Say 'Not Secure'?

What's happening

"Not Secure" means the browser can't confirm your site has a working SSL certificate, the piece that encrypts the connection and proves the site is really yours. It almost always comes down to a missing, expired or misconfigured certificate, not a hack.

You or your visitors might see "Not Secure" next to your web address, or a full-page "Your connection is not private" warning before the site will even load. Both point to the same piece.

Why it happens

The usual causes are straightforward: your site has no SSL certificate at all, the certificate expired and didn't renew, it was issued for the wrong address, the site still opens at its old "http" address instead of the secure "https" one, or a page is loading some content over an old insecure link ("mixed content"). Certificates also renew on a schedule — when that quietly fails, a site that was fine yesterday suddenly starts warning people.

What you can safely try

• Check whether it's the whole site or one page — mixed-content warnings often hit specific pages.
• Note whether it started on a certain date — that usually points to an expired certificate.
• Don't ignore it — the warning drives visitors away and search engines rank secure sites higher.
• Avoid panic-buying random SSL products before the actual cause is known.

When to call us

The fix is making sure a valid certificate is installed, set to renew automatically, and that your whole site loads securely — no more warnings. On our care plans, every site gets HTTPS with certificates issued and renewed automatically, so this simply stops being something you have to watch. Send it our way and we'll clear the warning.