You open your own website and there it is, right next to your address: a gray “Not Secure” label, or worse, a full-page warning telling visitors to turn back. It’s an alarming thing to see, especially if you run a small business and your site is where customers find you, book with you or pay you.
The good news is that the “Not Secure” warning almost always comes down to a handful of fixable causes, and most of them take minutes, not days. In this guide, we’ll explain what the warning means, why it matters more than ever, and walk through how to fix it step by step, even if you’re not technical.
What the “Not Secure” Warning Actually Means
Browsers show “Not Secure” when the connection between a visitor and your website isn’t fully encrypted. In plain English, your page is being loaded over HTTP instead of HTTPS, or it’s loading over HTTPS but something on the page isn’t.
HTTPS depends on an SSL certificate (technically a TLS certificate today, though almost everyone still says “SSL”). The certificate proves your site is really yours and scrambles the data that travels between your server and the visitor’s browser, so nobody in between can read or change it. Without it, anything typed into your site, from a contact form to a login, travels in plain text.
Why It Matters More Than Ever
For years, the warning was a small gray label most people ignored. That’s changing. Google has announced that Chrome now asks visitors for permission before opening public sites that only work over HTTP. That means a visitor may hit a warning screen before they ever see your homepage.
Here’s what an insecure site can cost you:
- Lost visitors: many people leave the moment they see a security warning.
- Lost trust: customers are far less likely to fill in a form or buy from a site labeled “Not Secure.”
- Weaker SEO: Google has used HTTPS as a ranking signal for years.
- Real risk: passwords, emails and payment details sent over HTTP can be intercepted, especially on public Wi-Fi.
The 5 Most Common Causes (and How to Fix Each One)
1. You don’t have an SSL certificate installed
This is the most common cause on older sites. If your address starts with http:// and typing https:// gives you an error, there’s no certificate in place.
How to fix it: log in to cPanel and look for SSL/TLS Status. Most hosts, including AthenaHost, offer a free certificate you can issue for your domain with a click or two. If you’re wondering whether you need something more, our guide to free SSL vs. paid SSL explains when a paid certificate makes sense. For most small-business sites and blogs, a free certificate is all you need.
2. Your certificate has expired
Certificates don’t last forever, and their lifespans are getting shorter. Under industry rules adopted by the CA/Browser Forum, publicly trusted certificates issued from March 15, 2026 can be valid for a maximum of 200 days. That drops to 100 days in March 2027 and to 47 days in March 2029.
How to fix it: renew the certificate in cPanel, then make sure AutoSSL (automatic renewal) is turned on. With renewals coming this often, renewing by hand is a reminder you’ll eventually miss. Automatic renewal is the only realistic option going forward.
3. Your site still loads on HTTP
Sometimes the certificate is installed and working, but your site doesn’t force visitors onto the secure version. Anyone who types your domain without “https” or clicks an old link ends up on the insecure page.
How to fix it: set up a permanent (301) redirect from HTTP to HTTPS. In cPanel, open Domains and switch on Force HTTPS Redirect for your domain. On WordPress, also go to Settings → General and make sure both the WordPress Address and Site Address begin with https://.
4. Mixed content on the page
This is the sneaky one. Your page loads over HTTPS, but an image, script, font or video on it is still being pulled from an http:// address. Browsers flag the whole page as not fully secure, or quietly block the insecure item, which can break your layout.
How to fix it:
- Open the page in Chrome, right-click, choose Inspect and open the Console tab. Mixed content warnings list the exact files causing trouble.
- Update those links from
http://tohttps://in your page, theme or widget settings. - On WordPress, a search-and-replace plugin can update old
http://yourdomain.comlinks across your whole database at once. Take a full backup first. - Clear your site cache and your browser cache, then reload the page.
5. The certificate doesn’t match your domain
A certificate issued for example.com won’t automatically cover www.example.com or shop.example.com. Visitors on the uncovered version see a “Your connection is not private” error instead.
How to fix it: reissue the certificate so it includes every version of your domain you use, both with and without “www” plus any subdomains. Then pick one main version and redirect the others to it.
Quick Diagnosis: What Your Browser Is Telling You
| What you see | Likely cause | First thing to try |
|---|---|---|
| “Not Secure” next to an http:// address | No SSL, or no HTTPS redirect | Install SSL and force HTTPS |
| Full-page “Your connection is not private” | Expired or mismatched certificate | Renew or reissue in cPanel |
| Padlock missing on some pages only | Mixed content | Check the browser console for http:// files |
| Warning appears on www but not without it | Certificate doesn’t cover www | Reissue to include both versions |
How to Keep the Warning From Coming Back
Once your padlock is back, a few habits will keep it there:
- Leave automatic renewal on. With shorter certificate lifespans, this is essential.
- Use https:// links whenever you add images, embeds or scripts.
- Re-check after big changes, like a new theme, a domain change or a move to a new host.
- Keep WordPress, themes and plugins updated, since security is about more than the padlock.
- Choose a host that handles SSL for you, so certificates are issued and renewed without you thinking about it.
Moving hosts? Our step-by-step guide on how to migrate your website without downtime covers what to check, including making sure HTTPS works on the new server before you switch your domain.
Frequently Asked Questions
Is a “Not Secure” website dangerous to visit?
Just reading a page usually isn’t risky. The danger is in sending information. Anything you type, such as passwords, emails or card numbers, can be intercepted on an unencrypted connection. Avoid entering personal details on a site marked “Not Secure.”
Do I need SSL if my site doesn’t sell anything?
Yes. Browsers warn about every HTTP page, not only checkout pages, and a contact form or login still collects information worth protecting. HTTPS also helps your search visibility.
How long does it take to fix the warning?
Installing a free certificate and turning on an HTTPS redirect usually takes a few minutes. Cleaning up mixed content can take longer on a large site, but a search-and-replace tool handles most of it in one pass.
Why did the warning appear when nothing changed on my site?
Usually an expired certificate is to blame. It can also happen after a browser update tightens its security rules. Check the certificate’s expiration date first.
Conclusion: Get Your Padlock Back
The “Not Secure” warning looks scary, but it’s one of the most fixable problems a website can have. Install a certificate, force HTTPS, clean up mixed content and leave automatic renewal on, and your visitors will see a site they can trust.
If you’d rather not deal with certificates at all, AthenaHost makes it simple. Our shared hosting plans start at $7.95/mo, our WordPress hosting is built for busy site owners, and every plan includes free site migration, so we can move your site over and get your padlock showing. Compare plans and pick the one that fits your business.