"Not secure" in the browser — why your site says it and how to fix it

You bought a domain, deployed the site, open it — and the address bar says a grey "Not secure." Or worse: a full-page red warning with a "back to safety" button. You can't show that to your first visitors: half of them close the tab and never come back.
Good news — there are only three causes, and they differ by symptom. Start with what the browser is actually showing.
A quick fork:
- Page loads, no padlock or a grey one → there's no certificate at all, you're on
http. Cause 1. - Page loads, padlock present but with a warning → mixed content. Cause 2.
- Page doesn't load, red screen with a code like
ERR_CERT_...→ there is a certificate, but the wrong one or an expired one. Cause 3.
Let's go through them, most common first.
Cause 1. There's simply no certificate
The most common beginner case. The site runs on plain http, and Chrome now marks any such page "Not secure" — even with no form and no password on it.
What a certificate is and why you need one is covered in the piece on HTTPS. What matters here: a certificate doesn't appear by itself, it has to be issued. Usually that's free and one click — your host goes to Let's Encrypt for you.
How to check. Type the address by hand with https:// in front. If the page doesn't load at all, there's no certificate. If it loads with a padlock, the certificate exists — your site just isn't redirecting http to https (more below).
How to fix. In your hosting panel find the SSL / TLS section and enable the automatic certificate. If the toggle is already on but nothing issues, DNS is nearly always to blame: to issue a certificate, the authority visits your domain and checks it points at your server. So:
- verify the domain's A record points to your server's IP;
- give the records time to propagate — usually minutes, occasionally hours;
- if the domain is brand new, check the guide on connecting a domain;
- then reissue the certificate from the panel.
Once the certificate is live, turn on the http → https redirect. Otherwise some visitors and search crawlers keep hitting the old address and keep seeing "Not secure."
Cause 2. One http image breaks the whole page
Different symptom: the page loads over https, but the padlock carries a warning, and sometimes images vanish or the layout falls apart.
This is mixed content: the page itself is secure, but something inside it loads over open http. The browser reasons soundly — a channel is only as protected as its weakest link.
It behaves differently per resource type. Scripts and stylesheets over http are blocked outright — hence "the site suddenly lost its design." Images the browser tries to fetch over https itself, and if that fails, it just doesn't show them.
How to check. Open DevTools (F12) → Console tab. Look for lines saying Mixed Content — the offending URL is printed right there.
How to fix. Find http:// in your code and replace it with https://. Most often it's:
- links to third-party images and fonts;
- a library included via an old URL;
- your own domain hardcoded in a config;
- an image URL copied out of an old article.
One extra trap: if an AI agent assembled your landing page, it may well have inserted http:// links to demo images. Check those first.
Cause 3. There is a certificate, but the wrong one
Here the browser won't let you through: a full-screen warning and an error code. The code is the diagnosis — read it.
ERR_CERT_COMMON_NAME_INVALID — the certificate isn't for this domain. The classic: issued for example.com, but you opened www.example.com. To a browser those are different names. Fix by issuing for both (panels usually have an "include www" checkbox) and redirecting one to the other.
ERR_CERT_DATE_INVALID — expired. Free Let's Encrypt certificates live about 90 days and renew automatically. If renewal broke (the IP changed, a service died, port 80 got closed for the check), the certificate quietly expires — and the site goes down one day with no code change at all. Fix by reissuing and confirming the renewal job is alive.
The same error can appear through no fault of yours: if a visitor's device clock is wrong, a valid certificate looks "not yet valid." Check the date on your own machine before you go fixing the server.
ERR_CERT_AUTHORITY_INVALID — a self-signed certificate. You issued it yourself and the browser has no reason to trust it. Fine for local development, not for a live site: get one from a real authority.
The checklist, if you're in a hurry
- Open the site with an explicit
https://— is there a certificate at all? - No → enable SSL in the hosting panel, check the domain's A record, reissue.
- Yes, but with a warning → DevTools → Console → look for
Mixed Content, swaphttp://forhttps://. - Red screen → read the error code: wrong domain, expired, or self-signed.
- All green → enable the
httptohttpsredirect and test both thewwwand non-wwwaddress.
Why did "not secure" appear on its own after a year?
Almost certainly an expired certificate: auto-renewal broke silently a couple of months ago. The second most common cause is a new block you added with a third-party image over http.
Can I just click "proceed anyway"?
For yourself, sure, to take a look. Don't show that to visitors: hardly anyone reaches the button, and search engines will demote the site. While the red screen is up, your site effectively doesn't exist for people.
Do I need a paid certificate?
For an ordinary site, no. A free Let's Encrypt certificate encrypts exactly the same way, and the browser makes no distinction. Paid certificates are for rare corporate scenarios, not side projects.
The AI Architect 2027 course: step by step from computer basics to your own app and first customers. 543 short lessons on your phone.





