Website Says Not Secure? 7 Causes and How to Fix Each One
Written by ismysiteup
If your website says "Not secure" in the address bar, or visitors get a full-page "Your connection is not private" warning, the browser has found a problem with how your site uses HTTPS. The fix depends on which of seven causes is behind it: an expired certificate, a missing intermediate certificate, mixed content, a hostname or www mismatch, no redirect from HTTP to HTTPS, a self-signed certificate, or a wrong clock on the visitor's device. This guide shows how to check each one and fix it, usually in under an hour.
Short answer: if the page loads but says "Not secure", the page or some of its files are on http://. If the browser blocks the page with a full-screen warning, the certificate itself is the problem: expired, for the wrong name, missing its chain, or self-signed.
What "not secure" means on a website
A "Not secure" label means the connection isn't fully encrypted, or the browser can't confirm it is really talking to your site. Anything typed into the page could be read or changed on the way.
Browsers show two very different kinds of warning, and telling them apart saves a lot of time:
- A "Not secure" label with the page still loading behind it. The connection worked, but it isn't fully HTTPS. Look at the redirect and mixed content first (causes 3 and 5).
- A full-page warning such as "Your connection is not private" (Chrome, Edge) or "Warning: Potential Security Risk Ahead" (Firefox). The browser refused the certificate. Look at causes 1, 2, 4, 6 and 7.
This matters more than it used to. Since Chrome 154 (October 2026), Chrome tries HTTPS first for every public site and asks the visitor for permission before opening a page that only works over plain HTTP.
Website says not secure? Match the warning to the cause
Click the icon to the left of the address, or read the small error code under the warning, then find it here.
| What you see | Error code (Chrome / Firefox) | Most likely cause |
|---|---|---|
| "Your connection is not private" on every device | NET::ERR_CERT_DATE_INVALID / SEC_ERROR_EXPIRED_CERTIFICATE | 1. Expired certificate |
Works on your laptop, fails on some phones, apps or curl |
NET::ERR_CERT_AUTHORITY_INVALID / SEC_ERROR_UNKNOWN_ISSUER | 2. Missing intermediate chain |
| "Not secure" label or broken padlock, page loads fine | Console: "Mixed Content" | 3. Mixed content |
Warning on example.com but not www.example.com (or the reverse) |
NET::ERR_CERT_COMMON_NAME_INVALID / SSL_ERROR_BAD_CERT_DOMAIN | 4. Hostname or www mismatch |
"Not secure" when someone types the address without https:// |
None, or Chrome's "Connection is not secure" prompt | 5. No HTTP-to-HTTPS redirect |
| Warning on a new site or server, issuer is your own server or host | NET::ERR_CERT_AUTHORITY_INVALID / SEC_ERROR_UNKNOWN_ISSUER | 6. Self-signed or default certificate |
| Only one visitor sees it, often "Your clock is behind" | NET::ERR_CERT_DATE_INVALID | 7. Wrong device clock |
Test from a second device on mobile data, or paste the https:// address into our free instant website checker, which shows the status code, response time and SSL details. If only one device complains, start with cause 7.
1. Your SSL certificate has expired
Every certificate has an end date. The moment it passes, every browser shows a full-page warning, and most visitors leave. It's the most common reason a website is suddenly not secure, usually because auto-renewal failed quietly.
How to check: click the warning, then "Certificate" or "View certificate" and read the "Valid to" or "Expires on" date. Our guide on how to check when an SSL certificate expires covers every browser and the command line.
How to fix: renew the certificate in your hosting panel, or run your renewal tool (for example certbot renew) and reload the web server. Then find out why auto-renewal failed, or it will happen again. For the business cost of this mistake, see why SSL expiry is a silent outage.
2. The intermediate certificate chain is missing
Your certificate is signed by an intermediate certificate, which is signed by a root the browser trusts. Your server has to send both your certificate and the intermediate. If it only sends its own, many desktop browsers fill the gap from their cache, so the site looks fine to you, while some phones, older devices, apps and API clients reject it.
How to check: run this from a terminal (replace the domain):
openssl s_client -connect example.com:443 -servername example.com -showcerts </dev/null
Count the certificates in the output. If there's only one, or the last line says Verify return code: 21 (unable to verify the first certificate), the chain is incomplete. A healthy result ends with Verify return code: 0 (ok).
How to fix: install the full chain file your certificate authority gave you. It's usually called fullchain.pem, a "CA bundle" or "certificate chain". In Nginx, point ssl_certificate at the full chain file. On hosting panels, paste the CA bundle next to the certificate, or reinstall with the host's free SSL tool.
3. Mixed content: HTTPS page, HTTP files
This is the classic reason a website says not secure even though the certificate is valid. The page itself loads over HTTPS, but an image, script, stylesheet, font, video or iframe is still loaded from an http:// address. Browsers block or upgrade much of this automatically, but whatever's left can cost you the padlock or break parts of the page.
How to check: open the page, press F12 (or right-click and choose Inspect), open the Console tab and reload. Each mixed content warning names the exact http:// file. Check a few page types, because mixed content is often only on some pages.
How to fix:
- Change each
http://link tohttps://, or to a relative path such as/images/logo.png. - If a third-party file has no HTTPS version, host it yourself or remove it.
- On WordPress, set both addresses in Settings > General to
https://, then replace old URLs in the database with a search-and-replace plugin or WP-CLI:wp search-replace 'http://example.com' 'https://example.com'. Back up first. This is the usual fix when a WordPress website says not secure after switching to HTTPS. - As a stopgap, the header
Content-Security-Policy: upgrade-insecure-requestsmakes browsers fetch those files over HTTPS.
4. The certificate doesn't match the hostname (www vs non-www)
A certificate only covers the names listed in it. A certificate for example.com does not automatically cover www.example.com, and a wildcard *.example.com covers www.example.com but not the bare example.com. Visit a name that isn't listed and the browser shows NET::ERR_CERT_COMMON_NAME_INVALID.
How to check: open all four versions of your address: http:// and https://, each with and without www. To list the names a certificate covers:
openssl s_client -connect example.com:443 -servername example.com </dev/null 2>/dev/null | openssl x509 -noout -ext subjectAltName
How to fix: reissue the certificate with every hostname you use (most hosts and Let's Encrypt let you add www and the bare domain to one certificate). Then pick one main version and redirect the other to it. A redirect alone doesn't help, because the browser checks the certificate before it follows the redirect.
5. There's no redirect from HTTP to HTTPS
You may have a good certificate, but anyone who types example.com or follows an old link may land on the http:// version. That page shows "Not secure", and in current Chrome it can trigger a warning before the page even opens.
How to check: in a private window, type your domain without https://. Or run curl -sI http://example.com and look for a 301 response with Location: https://....
How to fix:
- Turn on "Force HTTPS" or "Always use HTTPS" in your host, website builder or CDN settings. Most platforms have a single switch.
- On your own server, add a permanent (301) redirect from HTTP to HTTPS for every hostname.
- Update internal links, canonical tags and your sitemap to
https://. - Once everything works, add an HSTS header so returning browsers never try HTTP again.
6. The certificate is self-signed or a server default
A self-signed certificate was created by the server itself, not by a trusted certificate authority, so every browser rejects it. It's common on a brand-new site or after moving hosts, when the server shows a default certificate because the real one hasn't been issued yet. That's the usual answer to "why does my new website say not secure".
How to check: open the certificate details. If the issuer is your server name, your hosting company's panel, or the same as the "issued to" name, it's self-signed or a placeholder.
How to fix: install a certificate from a trusted authority. Let's Encrypt certificates are free, and most hosts and website builders issue one automatically once your domain points at them. If you just changed DNS, wait for it to update, then run the host's SSL tool again.
7. The visitor's device clock is wrong
Browsers check the certificate's dates against the device's clock. If a laptop's date is months off, a valid certificate looks expired or "not yet valid", and Chrome often says "Your clock is behind" or "Your clock is ahead". Only that one device is affected.
How to fix: on the affected device, turn on automatic date, time and time zone, then reload. Antivirus "HTTPS scanning" and public Wi-Fi login pages can cause similar warnings.
How to stop "not secure" warnings coming back
Once the chain, hostnames, redirects and links are right, they stay right until someone changes the server. The cause that keeps coming back is expiry, because renewals fail without telling you.
That's where monitoring helps. With ismysiteup, you add your site and get warned early when its SSL certificate is close to expiry, so you can renew before visitors see a warning. The same monitor checks the site around the clock and sends an alert the moment a check fails, plus a recovery message when it's back.
Alerts go wherever you'll actually see them: WhatsApp, Telegram, Slack or email, on every plan, including Free. Our setup guides cover WhatsApp website down alerts, Telegram alerts and Slack alerts.
The Free plan includes five uptime monitors checked every 5 minutes. Pro (listed at $9/month) checks every minute and Business (listed at $24/month) every 30 seconds. See the pricing page for current details and availability.
FAQ
Why does my website say not secure even though I have an SSL certificate?
Usually because of mixed content (some images or scripts still load over http://), a missing HTTP-to-HTTPS redirect, or a certificate that doesn't cover the exact hostname, such as www. Check the browser console and test every version of your address.
What does "not secure" mean on a website?
It means the connection isn't fully encrypted, or the browser can't verify the site's certificate.
Why is my website suddenly not secure?
If it worked yesterday, the certificate has most likely expired or failed to renew. A recent server move, a new CDN or plugin, or a changed DNS record can also swap or remove the certificate.
How do I fix "not secure" in Chrome?
Click the icon next to the address and read the error code. Then renew or reissue the certificate, install the full chain, redirect HTTP to HTTPS and fix any mixed content shown in the console. Retest in a private window.
Why does my website say not secure on Safari or iPhone only?
Phones are stricter about a missing intermediate certificate, and an iPhone with the wrong date shows the same warning. Check your chain with an SSL checker, and check the device's date and time settings.
Does a "not secure" warning hurt SEO?
Indirectly, yes. Google uses HTTPS as a ranking signal, but the bigger cost is visitors leaving when they see a warning. Fix the cause and keep your sitemap on https://.
Related reading: Why is my website down? 10 causes | WordPress site down? A recovery checklist | Website not working in other countries?
Sources
- Check if a site's connection is secure - Computer - Google Chrome Help, Google Chrome Help
- Mixed content - Security | MDN, MDN Web Docs
- SSL Server Test (Powered by Qualys SSL Labs), Qualys SSL Labs
- Expiration Notification Service Has Ended - Let's Encrypt, Let's Encrypt
- Ballot SC081v3: Introduce Schedule of Reducing Validity and Data Reuse Periods | CA/Browser Forum, CA/Browser Forum
Related Posts
How to Check When an SSL Certificate Expires (3 Easy Ways)
How to check when an SSL certificate expires in any browser, with one openssl command, or with a free online checker, plus how to get warned before it does.
Website Not Working in Other Countries? Here's Why (and How to Check)
Your site loads for you but not for visitors abroad? Here's why a website is not working in other countries, and how to check it from different locations.
SSL Certificate Expiry: The Silent Outage That Costs You Sales
An expired SSL certificate takes your entire site offline and shows visitors a scary security warning — but it's 100% preventable with a simple reminder.
How to Check If an App Is Down (or If It's Just You)
Here's how to check if an app is down for everyone or just you: a 60-second outside check, a 7-step checklist for when it only fails for you, and service-specific tips for ChatGPT, Instagram, WhatsApp and more.
Monitor your websites for free
Get instant email, Telegram, and WhatsApp alerts when your sites go down. Free plan checks every 10 minutes. No credit card required.
Start Monitoring Free