How to Fix the “Not Secure” Address Bar Error

You finally installed your SSL certificate, but your browser is still stubbornly shouting “Not Secure” in the address bar.

You try pulling the site up on your phone or a different browser, and it looks perfectly fine. Beautiful green padlock, completely secure. So why is your main browser gaslighting you?

If this sounds familiar, the issue usually boils down to a single moment: you accessed the site before the SSL was set up and bypassed the browser warning.

When you click “Advanced” and proceed to an insecure site, your browser creates a persistent security exception. Even after you install a pristine SSL certificate, the browser often refuses to re-verify the site, clinging instead to its cached memory of that initial insecure connection. If you are stuck in this loop, a standard page refresh won’t fix it. Here is how to break the cycle by clearing your browser’s HSTS and SSL cache.

 

Clear Your Browsers HSTS/SSL State

Step 1: Wipe the Domain Security Policies (HSTS Cache)

Chromium-based browsers (like Google Chrome, Microsoft Edge, and Brave) keep a strict registry of security policies for domains you visit. To force the browser to look at your site with fresh eyes, you need to manually delete your domain from this internal list.

Open your browser and in the address bar type:

• chrome://net-internals/#hsts
• edge://net-internals/#hsts
• brave://net-internals/#hsts

Scroll to the very bottom of the page until you see the Delete domain security policies section.

In the Domain text box, type your website’s clean domain name (for example, endurtech.com). Be sure to not include http://, https://, or any slashes.

Click the Delete button and move onto step 2 below.

Note: The page won’t give you a flashy success message; it will just quietly clear the entry.

 

 

Step 2: Perform a Full Browser Relaunch

Clearing the policy registry is only half the battle; the browser’s active session memory needs to be fully reset to apply the change.

Close all open windows and tabs of your browser to completely kill the background processes. You may even need to restart your PC.

Reopen the browser and visit the website in question. our browser should now bypass its old cache, fetch the live site data, discover the newly active SSL certificate, and display the proper secure padlock icon.

Still Seeing the Warning? Check for “Mixed Content”

If you followed these steps and the warning refuses to budge, your browser might actually be telling the truth about a new issue: Mixed Content.

This happens when your website itself loads over https, but individual elements inside the code—like images, scripts, or fonts—are still hardcoded to fetch over old http:// links.

To check for this, right-click anywhere on your website, click Inspect, and view the Console tab. If you see mixed content warnings, updating those internal file paths to https will secure your site once and for all. You can hire me for assistance.

 

Conclusion

As always, I welcome your thoughts, questions or suggestions on my article on how to resolve the “Not Secure” notice within your browsers’ address bar.

You may support my work by sending me a tip using your Brave browser or by sending me a one time donation using your credit card.

Let me know if you found any errors within my article or if I may further assist you by answering any additional questions you may have.