A "Not Secure" label means your browser could not set up a valid, encrypted HTTPS connection with that page. It does not mean the site was hacked, and it does not prove the site is safe or unsafe. If you are a visitor, keep passwords and card numbers out of it. If you own the site, the cause is one of a short list, and the diagnosis table below tells you which one from what you see.
- I am a visitor and I saw the warning
- I own the site and need to find the cause
- I just want the HTTPS migration checklist
Is it safe to visit a website that says Not Secure?
Reading a page is usually low risk. Typing into it is the risk. On a plain HTTP page, anyone positioned on the network path between you and the site (shared Wi-Fi, a compromised router, a hostile network) can read what you send and, in some cases, change what you receive. A contact form, a login, or a card number should never go through that.
The reverse also holds. A padlock or a missing warning does not make a site honest. Phishing sites run on HTTPS all the time, so check the domain name itself before you trust any page with a login.
What should I do when a page says Not Secure?
- Do not enter passwords, card numbers, or personal details on that page.
- Check the spelling of the domain. A look-alike name is a bigger red flag than the label.
- Try the address with
https://typed in front. Many sites support it and just do not redirect. - If it is a site you use all the time and it worked yesterday, check your device's date and time, then try another network or mobile data. A wrong clock or a public Wi-Fi sign-in page can break HTTPS for every site at once.
- If the site is a business you want to deal with, tell them. Apple's guidance for Safari says the same: if you need to use the site, contact its owner or administrator and say it is not secure.
What happens if you accidentally click on an unsecure website?
Usually nothing. Loading an HTTP page is not the same as catching a virus. The exposure comes from what you do next: typing a password or payment detail, or downloading a file from a page you cannot verify. If you already entered a password, change it on the real site, and change it anywhere else you reused it. If you downloaded something, scan it before opening it.
How do I enter a site that is not secure?
You have to choose it on purpose. If Chrome's "Always use secure connections" setting is on, Chrome shows a prompt before loading a public HTTP site, with Continue to site and Return buttons. Firefox's HTTPS-Only Mode shows a "Secure Site Not Available" page with a Continue to HTTP Site button. For an expired or invalid certificate, Chrome shows a full-page "Your connection is not private" screen with an Advanced link that lets you proceed, and Safari has a similar details option.
Proceed only for something you would read on a postcard: a public article, a document you are only viewing. Never to log in, buy, or submit a form.
How do I turn off the unsafe website warning?
In Chrome, open chrome://settings/security and turn off "Always use secure connections." In Firefox, turn off HTTPS-Only Mode in Settings. I would leave them on. The warning is the browser doing its job, and switching it off only hides the problem on every site, not just the one annoying you. If a warning appears on a device on your own network, such as a router page or a local test server, Chrome's public-sites setting does not prompt for private addresses like 192.168.0.1 or single-label hostnames.
Why is Chrome suddenly saying everything is not secure?
The answer depends on whether it is every site or one site.
- It is new HTTP prompts everywhere: Google's Chrome Security team announced in October 2025 that it would turn on "Always Use Secure Connections" for public sites for Enhanced Safe Browsing users in Chrome 147 (April 2026) and for everyone by default in Chrome 154 (October 2026). Many HTTP links used to redirect to HTTPS so quickly that nobody noticed. Chrome now tries HTTPS first and asks before loading a public site that cannot do it. Check your version at
chrome://settings/help. - It is every HTTPS site showing "Your connection is not private": suspect your device clock, a captive portal on public Wi-Fi, an antivirus or VPN that intercepts HTTPS, or a device with outdated root certificates.
- It is one site: the problem is that site's certificate, redirects, or content. The owner sections below cover it.
Why does Safari keep telling me this connection is not secure?
Apple lists four causes: the site is encrypted but its certificate expired or is not legitimate, the certificate is valid but the site uses TLS 1.1 or older, the site is not encrypted and asks for a password or card number, or the site uses HTTP instead of HTTPS. If it happens on many sites, look at your clock, your network, and any security software. Apple's advice is the same in every case: never enter your password or credit card number on a site showing the warning.
What "Not Secure" means, and what it does not
TLS, still often called SSL, protects the connection between a browser and a server. It encrypts data in transit, helps stop it being changed on the way, and lets the browser confirm the server holds a certificate for the domain you typed. The "s" in https:// means that layer is in use.
An HTTP connection has none of that. The label shows up for the connection, so it appears on every HTTP page, not only checkout pages.
HTTPS does not certify that the business is honest. It does not scan the site's code, remove malware, or stop a stolen administrator password. Chrome changed its icon in version 117 partly because people read the old lock as "this site is trustworthy." The Chromium explanation is plain about that, and it also says Chrome will keep marking plaintext HTTP as insecure on all platforms. Any guide that says "look for the padlock" as the whole test is out of date. For the technical definition, use MDN's TLS reference.
What the main browsers show
| Browser | Plain HTTP page | Certificate problem or no HTTPS option |
|---|---|---|
| Chrome | "Not secure" in the address bar. Since Chrome 117 a working HTTPS page shows a site-controls icon, not a lock, and no warning. | Full-page "Your connection is not private" with a code such as NET::ERR_CERT_DATE_INVALID. With "Always use secure connections" on, a prompt appears before a public HTTP site loads. |
| Safari | Apple lists "Not Secure," "Website Not Secure," and "This Connection Is Not Secure" as the warnings. | Per Apple: an expired or illegitimate certificate, or TLS 1.1 or older, triggers the connection warning. |
| Firefox | Marks the page as not secure in the address bar. | With HTTPS-Only Mode on, a "Secure Site Not Available" page offers Continue to HTTP Site or Go Back. |
Edge, Brave, and Opera are built on Chromium and behave similarly, though labels change between versions. If your screen does not match, check the version first.
Why an insecure connection still matters to a business
A contact form can carry names, email addresses, phone numbers, and project details. That data should not cross an unprotected connection. Browsers also limit some features to secure contexts, and payment providers generally require HTTPS for live checkout.
The warning is also plain friction. A first-time visitor who sees "Not Secure" before they see anything you built may leave, and you would never know, because your analytics cannot count people who left before the page or tracking code loaded. I am not going to invent a conversion percentage for that.
On search: Google called HTTPS a very lightweight ranking signal back in 2014. Today its page-experience documentation lists secure serving as something to check, and says Core Web Vitals are the part its ranking systems use directly. Fix HTTPS because the connection should be protected, not for a ranking jump.
HTTPS is connection security. It is necessary plumbing, not a trust badge for the whole business.
Wondering if this applies to your site?
The $500 SEO Health Check includes a written report within 48 hours and a 30-minute walkthrough after delivery.
Site owners: find the cause from what you see
Start with what the browser shows, not with a guess. Each row below points to the check in the next section.
| What you see | Likely cause | First check | Fix |
|---|---|---|---|
"Not secure" in the address bar, URL starts with http:// | No certificate, or HTTPS exists but nothing sends people to it | Request the HTTP URL with curl and read the status and Location header | Install a certificate, then add a permanent redirect to HTTPS |
Full-page "Your connection is not private," code NET::ERR_CERT_DATE_INVALID | Expired certificate (or, for one visitor only, a wrong device clock) | Read the certificate dates with openssl | Renew, then repair the automatic renewal that failed |
NET::ERR_CERT_COMMON_NAME_INVALID | The certificate does not cover this hostname, often www versus the bare domain, or a subdomain | List the names on the certificate | Reissue it to cover every hostname you serve |
NET::ERR_CERT_AUTHORITY_INVALID | Self-signed certificate, or a missing intermediate certificate | Check the chain with an SSL test or openssl | Use a public CA and install the full chain |
| HTTPS loads but the page is unstyled, images are missing, or a widget is dead | Mixed content: an HTTP script, stylesheet, or iframe was blocked | Open DevTools and read the Console and Issues tabs | Change those URLs to HTTPS or host the file yourself |
https:// works on one hostname but www or the HTTP URL fails or never redirects | Redirect gap, or the second hostname has no certificate | Test all four variants (HTTP and HTTPS, with and without www) | Cover every hostname with a certificate and send all of them to one canonical URL |
| "Too many redirects" right after turning on HTTPS behind a CDN | The CDN talks to your server over HTTP while the server forces HTTPS | Look at the CDN's SSL mode | Use an end-to-end mode that validates the origin certificate, such as Cloudflare's Full (strict) |
| Works for you, warning for other people | Missing intermediate certificate, a cached old redirect, or a hostname you do not test | Test from another network and device, and with an outside SSL checker | Install the full chain and retest every hostname |
| Only the form or checkout page is flagged | A form posting to an HTTP address, or an HTTP embed on that page | Search that page's source for http:// | Change the form action and embeds to HTTPS |
Copy-paste checks
These take a minute and need nothing but a terminal and a browser. Replace example.com with your domain. (On Windows, use curl.exe in PowerShell.)
1. Test all four URL variants
curl -sI http://example.com/
curl -sI http://www.example.com/
curl -sI https://example.com/
curl -sI https://www.example.com/
Healthy looks like this: both HTTP lines return 301 or 308 with a Location: header pointing at your one canonical HTTPS URL. The canonical HTTPS URL returns 200. The other HTTPS hostname either returns 200 or redirects to the canonical one. A certificate error from curl on any line is a finding, because that is the hostname a browser will warn about. Ideal is one hop: if http://www goes to http:// and then to https://, collapse the chain.
2. Read the certificate
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -subject -issuer -dates -ext subjectAltName
Check notAfter for the expiry date, and the subject alternative names for every hostname you serve. Run it again with www.example.com.
3. Read the browser's evidence
- Open the page, press F12, and open the Console. A blocked resource reads like this: Mixed Content: The page at 'https://example.com/' was loaded over HTTPS, but requested an insecure script 'http://cdn.example.net/app.js'. This request has been blocked; the content must be served over HTTPS. Wording varies by browser and version.
- Open the Issues tab. web.dev points there for mixed content, and it lists each insecure resource with its status.
- Open the Network tab and type
scheme:httpinto the filter to list requests that used HTTP. - For the certificate, open the site-controls icon in the address bar and view the connection details, or use the Security panel in DevTools (under More tools in recent Chrome). Menu names change between releases.
- For a form, view the page source and search for
http://near<form.
Repeat on a service page, the contact page, and any checkout or booking path. Do not stop at the homepage.
If you would rather paste a URL, my free HTTPS and mixed content checker tests the HTTP redirect, HSTS, the canonical protocol, and insecure resources in the page's HTML. It checks one URL at a time and cannot see resources a stylesheet or script pulls in later, so the DevTools check above is still the full test. The case study on how I built it covers what it does and does not detect.
Fix it by cause
No certificate yet
On a managed builder or host: Find the HTTPS or SSL setting, confirm which hostnames it covers, and confirm the domain is actually connected to the platform. The switch may issue a certificate without cleaning up old HTTP references or redirects.
On WordPress: Get the certificate at the host first. Then change the WordPress Address and Site Address to https://, and replace old http:// URLs stored in the database, since posts, widgets, and page-builder data keep their own copies. A plugin that rewrites URLs on the fly can hide the problem while you fix it, but it is a stopgap.
On shared hosting with cPanel: Look for AutoSSL or a Let's Encrypt option in the SSL/TLS section.
On a server you manage: Issue the certificate through an ACME client, configure the HTTPS virtual host, and automate and monitor renewal. This is server work. Guessing in production is a bad hobby.
Behind Cloudflare or another CDN: Use an SSL mode that validates your origin certificate end to end, then turn on the option that sends HTTP visitors to HTTPS. The "Flexible" style of mode, where the CDN fetches from your server over HTTP, is the usual source of redirect loops when your server also forces HTTPS.
Expired certificate
Fix issuance first, because browsers show a full-page warning before the site loads, and that looks worse to a visitor than no certificate at all. Then find out why renewal failed. Typical causes are a domain that no longer points at the host that was renewing it, a redirect or firewall rule blocking the certificate authority's validation request, or a paid certificate whose renewal nobody owned.
Lifetimes are also getting shorter. Let's Encrypt certificates last 90 days by default, and its documentation recommends renewing about every 60. Under the CA/Browser Forum's Baseline Requirements, the maximum validity of publicly trusted certificates dropped to 200 days on March 15, 2026, falls to 100 days on March 15, 2027, and reaches 47 days on March 15, 2029. Anything renewed by hand once a year is on borrowed time.
Name mismatch (www, subdomains, old domains)
A certificate covers specific names. One issued for example.com does not automatically cover www.example.com, shop.example.com, or the old domain you redirect from. Reissue it with every hostname that answers on port 443, or use a wildcard for subdomains.
This matters more now. Chrome tries HTTPS first, so if http://old-name.com only redirects and https://old-name.com has no working certificate, a visitor can get a warning before the redirect is ever reached. Give every old hostname a valid HTTPS endpoint that redirects to the canonical URL, or retire it.
Redirect gaps
If the HTTPS URL works but the HTTP version does not redirect, the certificate is only part of the job. People and crawlers still reach the old URL through saved links, old listings, and external pages. Send each HTTP URL to its HTTPS equivalent with a permanent server-side redirect, in one hop.
Consider HSTS only after every hostname works over HTTPS. It tells browsers to use HTTPS automatically on repeat visits. Start with a short max-age, and think hard before adding includeSubDomains or submitting to the preload list, because both are difficult to undo if one subdomain is not ready.
Mixed content
Mixed content happens when an HTTPS page requests something over HTTP. Per MDN, browsers upgrade images, audio, and video to HTTPS automatically, unless the host is an IP address. Scripts, stylesheets, iframes, fonts, fetch() and XHR requests are blocked.
So one old resource does not simply "break the padlock." The browser may upgrade it, block it, or report it in the console depending on the type, and a blocked script or stylesheet breaks the page for real. The address bar is not a reliable guide, so use DevTools.
Where the bad URLs hide: post content and widgets in the database, theme or page-builder settings, hard-coded template files, third-party embeds and tracking snippets, url() values in CSS, form actions, and canonical or Open Graph tags. A Content-Security-Policy: upgrade-insecure-requests header can upgrade requests as a safety net. It is not a replacement for fixing the source, since a resource that does not exist over HTTPS still fails.
HTTPS migration checklist
Switching from HTTP to HTTPS is a site move. Google's site-move guidance recommends permanent redirects, matching canonicals, updated internal links, and monitoring after launch. Processing time and search movement vary, so do not promise a fixed recovery window.
- List every hostname that answers, including
www, subdomains, and old domains. - Get one certificate setup that covers all of them, with automatic renewal.
- Confirm all four URL variants load without a certificate error.
- Pick the canonical version and 301 every other variant to it in one hop.
- Update internal links, canonical tags, Open Graph URLs, hreflang, and structured data URLs to HTTPS.
- Update the sitemap and the
Sitemap:line in robots.txt. - Fix mixed content: database content, templates, CSS, embeds, forms, and third-party scripts.
- Update outside references you control: Google Business Profile, ad landing pages, email signatures, social profiles, payment and form-service callback URLs.
- Add the HTTPS property in Search Console and watch the HTTPS report, coverage, and crawl errors for a few weeks.
- Set an expiry alert at least 21 days before the certificate expires, and add HSTS last.
"My developer set up SSL already. Am I good?"
Maybe. Visit your homepage, then your contact page, a service page, and any booking or checkout page, and run the checks above on each. If one page shows a console error or a missing resource, something is still loading over HTTP. It is a five-minute fix for anyone who knows what they are looking at, and invisible to you unless somebody checks. If a developer quotes hundreds of dollars to turn on a free certificate and fix a few URLs, ask what exactly the quote covers and get a second opinion.
Do you need a paid certificate?
Not usually. Many hosting platforms support free, automatically renewed certificates, including Let's Encrypt, which is free to use. A paid certificate is not stronger encryption. What a paid one can add is organization validation, support, and a warranty, and browsers no longer give extended validation certificates a special address-bar treatment. The question that matters is operational: will the certificate renew, will every hostname stay covered, and will somebody notice before it expires?
What this article cannot tell you
- Whether a site is malicious. "Not Secure" and a lock both describe the connection only.
- How your specific host or theme stores old URLs. Platforms differ, and I am describing the common patterns.
- Exactly what your browser shows today. Chrome's HTTPS-by-default change is staged, and menu and label wording changes between releases. Check
chrome://settings/securityand your version. - What the warning costs you in leads. Nobody can measure that from analytics alone.
This is a baseline, not a bonus
Fix HTTPS before polishing title tags or publishing another article. If the connection layer is broken, the rest of the page is standing on it.
The SEO Health Check looks beyond the certificate at redirects, technical visibility, content, your Google Business Profile, and the path to contact. I name the problem, show the evidence, explain the likely consequence, and put the work in order.
Learn about the SEO Health Check →
FAQ
Does "Not Secure" mean my website has been hacked?
No. The warning alone means the browser did not establish a valid HTTPS connection for that page. It does not tell you whether the site was hacked, whether its code is safe, or whether the business is trustworthy.
How do I fix my website saying Not Secure?
Match what you see to the cause. No certificate: install one and redirect HTTP to HTTPS. Expired or mismatched certificate: renew or reissue it to cover every hostname. Page loads but looks broken: fix mixed content. Use the diagnosis table, then the migration checklist.
How do I make my website say secure?
Chrome no longer prints the word "Secure." A page with a valid certificate, an HTTPS URL, and no blocked mixed content simply shows no warning, with a site-controls icon in the address bar. Fix the cause of the warning and the label disappears.
Is it safe to go to a website that says Not Secure?
Reading is usually low risk. Entering passwords, payment details, or personal information is not. See the visitor section for what to do.
Does SSL affect my Google rankings?
Google recommends secure serving as part of a good page experience, but its page-experience documentation says Core Web Vitals are the part its ranking systems use directly. Do not treat HTTPS as a guaranteed ranking lift. Fix it because the connection should be protected, then judge search performance with real data.
Do I need to pay for an SSL certificate?
Not always. Many hosting platforms support free, automatically renewed certificates. The right choice depends on platform support, validation needs, and who will own renewal. A paid certificate is not automatically stronger encryption.
Will I lose my Google rankings when switching to HTTPS?
Search visibility may fluctuate while Google processes the URL change. Use permanent redirects, matching canonicals, updated internal links, and an updated sitemap. Monitor the move instead of promising a fixed timeline.
How do I know if my SSL is working correctly?
Confirm the page uses https://, inspect the browser's connection information and certificate, test the HTTP-to-HTTPS redirect for all four URL variants, and check the developer console for mixed-content messages. Repeat on representative pages, not only the homepage.
