Website Not Secure? 10 Steps to Fix it Fast

Website showing a Not Secure warning in a browser

A “Not Secure” warning means your browser could not confirm a fully encrypted HTTPS connection to your website. It does not mean your site was hacked.

It is usually one of four things. Your site loads over HTTP. Your SSL certificate has a problem. A page loads some files over HTTP (mixed content). Or a redirect or WordPress setting is wrong.

This guide covers what the warning means, why it happens, and, mostly, how to fix it step by step.

What Does “Not Secure” Mean on a Website?

“Not Secure” means the page was not delivered through a fully secure HTTPS connection. Chrome shows it in the address bar when a site uses HTTP, for example http://example.com. It can also appear when the SSL/TLS setup is faulty or when an HTTPS page loads insecure files.

Difference between HTTP and HTTPS website connections
  • HTTP (http://) is not encrypted. Data between the browser and server is not protected.
  • HTTPS (https://) uses TLS (Transport Layer Security) to encrypt that connection.

A hacked site looks different. You would see unknown content, unexpected redirects, malicious scripts or changed files. A “Not Secure” warning points to a connection or HTTPS setup problem.

The warning is also getting harder to ignore. From Chrome 154 (October 2026), Chrome asks for permission before it first opens a public site that does not support HTTPS. New visitors may see a full-page warning before your page loads.

WarningBrowserWhat it means
Not SecureChromePage uses HTTP or loads insecure files
Your connection is not privateChromeCertificate could not be validated
NET::ERR_CERT_DATE_INVALIDChromeCertificate expired, not yet valid, or the device clock is wrong
NET::ERR_CERT_COMMON_NAME_INVALIDChromeCertificate does not match the domain
NET::ERR_CERT_INVALIDChromeInvalid or unacceptable certificate setup
Secure Connection FailedFirefoxTLS or certificate problem on the server
Security certificate is not trustedEdge and older browsersBrowser does not trust the certificate

If you are a visitor and not the site owner, do not enter passwords, card details, or personal data on that page.

If a site you trust shows the warning, tell the owner.

And if every site shows a warning, check your device date and time, antivirus HTTPS scanning, and any VPN or proxy.

Why Is My Website Not Secure? 10 Common Causes

Common causes of a Not Secure website warning
  1. Your website still uses HTTP. The URL starts with http://.
  2. No SSL certificate is installed. Many hosts, like Hostinger, include free SSL through Let’s Encrypt.
  3. Your SSL certificate has expired. Public certificates now last 200 days at most, down from 398, and the limit falls to 100 days in March 2027. Missed renewals are easier now, so turn on auto-renewal.
  4. The certificate does not match your domain. A certificate for example.com may not cover www.example.com.
  5. The certificate is not trusted or is installed wrongly. The server may not send the full certificate chain.
  6. Your website has mixed content. An HTTPS page loads images, scripts, CSS, fonts or iframes over HTTP. This is common after a WordPress migration.
  7. HTTP to HTTPS redirects are wrong. Missing rules leave the HTTP version open. Conflicting rules cause redirect loops.
  8. WordPress still uses HTTP. The WordPress Address (URL) or Site Address (URL) was not updated.
  9. Your CDN or Cloudflare settings conflict with SSL. The browser talks to the CDN, and the CDN talks to your server. A mismatch causes errors.
  10. Your cache serves old HTTP files. The browser, a plugin, the host or the CDN can keep outdated URLs.

“Not Secure” is a symptom, not a diagnosis. Find the cause before you buy or reinstall an SSL certificate.

Website problems? We fix it!

Get urgent website issues fixed in 24 hours.

24 Hours

Delivery

On Priority

Assistance

Moneyback

Guarantee

Limited Slots

$59

How to Fix a Website That Says “Not Secure”

Follow the steps in order. Fixing mixed content is pointless if HTTPS itself does not work.

Website Not Secure troubleshooting flowchart

1. Check That HTTPS Loads

Open https://yourdomain.com in your browser. Test the www and non-www versions too. If you see a certificate error, go to Step 2. If it loads normally, go to Step 3.

2. Inspect Your SSL Certificate

Check these five things:

  • Domain name: does it cover the exact domain visitors use?
  • Expiry date: is it still valid?
  • Status: does the browser accept it?
  • Issuer: is it a trusted certificate authority?
  • Chain: does the server send the full certificate chain?

If any of these fail, renew, reissue or reinstall the certificate. Do not buy a new one first. Many sites already have a valid certificate, and the real problem is elsewhere.

3. Redirect HTTP to HTTPS

Test all four versions:

  • http://example.com
  • http://www.example.com
  • https://example.com
  • https://www.example.com

All four should end at one preferred HTTPS URL. The method depends on your host, server, CDN or WordPress setup.

4. Set Your WordPress URLs to HTTPS

Go to Settings > General and check the WordPress Address (URL) and Site Address (URL). Both should use https://. Change them only after HTTPS works. Otherwise, you will lock yourself out of the site.

5. Find Mixed Content

In Chrome, open the page, right-click and select Inspect, then open the Console tab. Look for messages that say Mixed Content. Chrome names the HTTP resource. Change its URL to HTTPS if the resource supports it.

Mixed content can be images, CSS, JavaScript, fonts, videos, iframes, tracking scripts or other external resources.

6. Replace Old HTTP URLs in WordPress

Old URLs hide in posts, pages, media, theme settings, plugins, widgets, Elementor data and the database. Back up your site first. Then use a WordPress-aware tool that handles serialized data, such as WP-CLI or the Better Search Replace plugin. Run a dry run before you apply changes:

wp search-replace 'http://example.com' 'https://example.com' --dry-run

If you use Elementor, also run Elementor > Tools > Replace URL.

7. Regenerate Elementor CSS

Elementor stores generated CSS and assets with the old URLs. Go to Elementor > Tools > Regenerate CSS & Data, then clear your other caches. If the Elementor editor itself breaks, see how to fix the Elementor editor not loading.

8. Check Plugins and Themes

The browser console shows which file loads over HTTP. Find the plugin, theme or external service behind it. If a plugin is causing the problem, update it and review its settings. For themes, check customizer settings and code for hard-coded HTTP URLs. Third-party scripts such as analytics, fonts and video players must support HTTPS.

Do not disable plugins at random. Identify the exact file first.

9. Fix Cloudflare or CDN SSL Settings

The path is visitor, then CDN, then origin server. Make sure the CDN’s SSL/TLS mode matches the certificate on your server. With Cloudflare, Full (strict) with a valid origin certificate is the safe choice. Flexible mode can cause redirect loops when your server also forces HTTPS. Keep HTTPS redirects in one place, not at both the CDN and the host.

If an SSL, DNS, redirect, or CDN problem stops your site from loading at all, follow our guide on how to fix a WordPress website that is not loading.

10. Clear Caches and Retest

Clear your caching plugin, server cache, CDN cache and browser cache. Then open the site in a private window and test the homepage, contact forms, login pages, checkout pages and landing pages. On each page confirm that:

  1. The URL uses HTTPS.
  2. No security warning appears.
  3. The console shows no mixed-content messages.
  4. Images and media load.
  5. CSS and JavaScript work.
  6. Forms and interactive elements work.

If the warning stays, return to the console. The remaining message usually names what is left to fix.

How to Fix “Not Secure” in Chrome

Chrome showing a Not Secure website warning

Chrome says “Not Secure”. The page is loading over HTTP. Try the https:// version. If it works, add a redirect (Step 3). If it shows a certificate warning, fix the certificate (Step 2).

Chrome says “Your Connection Is Not Private”. Chrome could not validate your certificate. Read the error code under the warning:

  • NET::ERR_CERT_DATE_INVALID: the certificate expired, is not yet valid, or the device or server clock is wrong. Check the dates and renew if needed.
  • NET::ERR_CERT_COMMON_NAME_INVALID: the certificate does not match the domain. Check the names it covers and test www and non-www.

To inspect a certificate in Chrome, click the site information icon left of the address bar, open the connection and certificate details, and review the domain, issuer and validity dates. Menu wording changes between Chrome versions.

To find hidden problems, open Inspect > Console and look for mixed content, blocked resources or certificate errors. If you do not see the Security tab, click the three-dot menu in DevTools, then More tools > Security.

Use the error code as your starting point. Do not keep reinstalling SSL.

SSL Is Installed, but My Website Still Says “Not Secure”

An SSL certificate secures the connection to your server. It does not rewrite every file URL on your pages. The usual cause is mixed content, so start with Step 5. Then work through Steps 6 to 10: old URLs in the database, stale Elementor assets, plugin or theme files, CDN settings and cache.

How mixed content causes HTTPS website security warnings

Do not replace your certificate unless Step 2 shows it is invalid.

Common SSL and HTTPS Errors and Fixes

Error or problemLikely causeWhat to check
Not SecureWebsite is using HTTPConfirm HTTPS is enabled and redirect HTTP to HTTPS
SSL installed but warning remainsMixed contentFind images, scripts, CSS, fonts, or other resources still using HTTP
Certificate expiredSSL certificate is past its validity periodCheck the certificate’s expiration date and renew or reissue it
Certificate mismatchCertificate does not cover the domain being accessedCheck the certificate’s domain names and test www and non-www versions
Your Connection Is Not PrivateCertificate validation or trust problemInspect the certificate, issuer, validity, and certificate chain
Too many redirectsConflicting HTTP/HTTPS redirect rulesCheck WordPress, server, CDN, and Cloudflare redirect settings
HTTPS works on one version onlywww/non-www configuration issueTest all domain variations and configure one preferred HTTPS version
CSS or JavaScript breaks after SSLResources are blocked or still referenced through HTTPInspect browser console and update insecure resource URLs
Site works after SSL installation but later breaksCache, CDN, hosting, or configuration issueClear caches and check recent configuration changes
Only one page is affectedPage-specific HTTP resource or embedded contentInspect that page’s resources and browser console

If your site becomes unstable after HTTPS changes and shows “There has been a critical error on this website,” read our guide on how to fix a WordPress critical error.

Website problems? We fix it!

Get urgent website issues fixed in 24 hours.

24 Hours

Delivery

On Priority

Assistance

Moneyback

Guarantee

Limited Slots

$59

How to Check That Your Website Is Fully Secure

A missing warning is not a full security check. Confirm each item:

  • HTTPS loads without a certificate warning.
  • The certificate is valid and matches your domain.
  • HTTP redirects to HTTPS.
  • www and non-www resolve to one preferred HTTPS version.
  • The console shows no mixed-content warnings.
  • Images, CSS and JavaScript load correctly.
  • Contact forms work.
  • Login, account and checkout functions work, where you have them.
  • Landing pages and service pages use HTTPS URLs.
  • Caches and CDN data are cleared.
Website Security Checklist

Frequently Asked Questions

Why is my website not secure?

Your site may use HTTP instead of HTTPS, have an expired or misconfigured SSL/TLS certificate, or load mixed content. WordPress settings, redirects, hosting, a CDN or caching can also cause it.

How do I fix a not secure website?

Find the cause first. Check that HTTPS loads, inspect your certificate, redirect HTTP to HTTPS, set your WordPress URLs to HTTPS, and fix mixed content. Then clear caches and retest.

Why is my website not secure even though I have HTTPS?

HTTPS on the page does not mean every file is secure. Images, CSS, JavaScript, fonts or iframes may still load over HTTP. This is mixed content.

Why does my WordPress website say “Not Secure”?

Common causes are HTTP site URLs, old HTTP links in the database, mixed content from plugins or themes, stale Elementor assets, wrong redirects, and CDN settings.

How do I fix a not secure website in Chrome?

Identify the warning first. Check that the site uses HTTPS, inspect the certificate, and open Inspect > Console to look for certificate or mixed-content errors. The error code points to the cause.

How do I remove the “Not Secure” warning?

Install a valid SSL/TLS certificate, load the site over HTTPS, redirect all HTTP traffic to HTTPS, and remove insecure HTTP files. Clear caches and retest.

Do I need to buy another SSL certificate?

Not always. If your certificate is valid and correctly installed, the cause is likely mixed content, redirects, WordPress settings, caching or your CDN. Diagnose first.

Can mixed content cause a “Not Secure” warning?

Yes. Use the browser console to find the insecure files and switch them to HTTPS where supported.

Is it safe to visit a website that says “Not Secure”?

It is risky to enter passwords, card details or personal data on it. Reading a page is lower risk, but the connection is not protected, so avoid logging in or paying.

Power Your Business with AI

Claim our free comprehensive kit to transforming your business using artificial intelligence.

Share This Post

Facebook
Twitter
LinkedIn

Need help?

Get a free consultation with our AI marketing experts.