"Not secure" website: what it means and how to fix it

4 min read
Illustration of a browser address bar showing the Not secure warning next to the site address

Summary: The "Not secure" warning appears when a page loads over unencrypted HTTP, when the certificate is missing, expired or doesn't cover the address used, or when there are problems with resources loaded without HTTPS. The fix is to install a valid certificate for every address of the site, redirect everything to HTTPS, fix mixed content and ensure automatic renewal.

You open your site and "Not secure" appears next to the address. Now imagine a customer seeing that before filling in your quote form. Chrome marks every page loaded over HTTP as not secure, and shows a privacy error screen when the certificate is invalid.

What an SSL/TLS certificate is

A file issued by a certificate authority proving the server answers for that domain and enabling an encrypted connection (the TLS protocol, successor to the old SSL). With it, the site opens with https:// and data typed by visitors is protected in transit between them and the server.

Why the warning appears: diagnosis

Causes and how to identify them
CauseSymptom
No certificate or accessed over http"Not secure" in the bar; the address starts with http://
Expired certificate"Your connection is not private" screen with error NET::ERR_CERT_DATE_INVALID
Certificate doesn't cover the addressError NET::ERR_CERT_COMMON_NAME_INVALID, e.g., certificate for yourcompany.com accessed as www.yourcompany.com
Incomplete chainWorks on some devices and fails on others
Mixed contentHTTPS page loading an image, script or form over http; the browser blocks or upgrades the resource and the console shows "Mixed Content"

To inspect: click the icon next to the address, then "Connection is secure" and "Certificate is valid" to see validity and covered names. Chrome DevTools (F12 → Console) shows mixed content warnings. From a terminal, this command shows issuer and validity:

openssl s_client -connect www.yourcompany.com:443 -servername www.yourcompany.com </dev/null 2>/dev/null | openssl x509 -noout -issuer -subject -dates

We also have a guide on how to test your SSL certificate.

How to fix it, step by step

  1. Install or renew the certificate on your hosting, covering the domain with and without www (and any subdomains in use).
  2. Set up automatic renewal. Maximum validity for public certificates dropped to 200 days on March 15, 2026, goes to 100 days in 2027 and 47 days in 2029 (CA/Browser Forum, Ballot SC-081v3). Manual renewal is no longer viable; use ACME (Let's Encrypt's protocol) or your host's automation.
  3. Redirect HTTP to HTTPS with a 301. Apache example:
    RewriteEngine On
    RewriteCond %{HTTPS} off
    RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
  4. Fix mixed content: change http:// to https:// in images, scripts, fonts, iframes and form action attributes. In a CMS, update the site URL in settings.
  5. Update canonicals, sitemap and internal links to the HTTPS URLs.
  6. In Search Console, use a domain property (covering HTTP and HTTPS) or add the HTTPS version.
  7. Optional, once stable: enable HSTS so browsers always use HTTPS (see the example in website security).

Does it affect Google?

Google has used HTTPS as a lightweight ranking signal since 2014 and considers it part of page experience (documentation). The bigger effect is on trust: security warnings drive visitors away and cut conversions. Google also recommends 301 redirects and HTTPS canonicals when migrating (site move with URL changes).

Free or paid?

The encryption is the same. Free certificates (Let's Encrypt) are domain-validated (DV) and serve institutional sites, blogs and most stores. Paid certificates make sense when you need organization validation (OV/EV), support, contractual warranty or certificates for specific uses. Browsers currently don't distinguish DV from OV/EV in the address bar.

On our hosting, the certificate is installed and renewed automatically. Need a certificate with organization validation? See SSL certificate. If your site shows a warning, our website maintenance team fixes it.

Sources and references

Frequently asked questions

Is a free SSL certificate trustworthy?

Yes. The encryption is the same as paid ones. The difference is in validation type, support and contractual guarantees.

What's the maximum certificate validity today?

Since March 15, 2026, 200 days. Under the CA/Browser Forum schedule, it drops to 100 days in March 2027 and 47 days in March 2029.

The site has a certificate but still shows "Not secure". Why?

Usually it's http access without a redirect, a certificate that doesn't cover the address used (with or without www) or resources loaded over http.

Does switching to HTTPS hurt SEO?

Done with 301 redirects and updated canonicals and sitemap, Google treats the migration as a URL change. There may be temporary fluctuation while pages are reprocessed.

Is your website showing a "Not secure" warning?

We install the certificate, fix mixed content and get your website showing the padlock.

Read also

Written by Mário Moreno, founder of Agência hetsi, which has been building websites and handling digital marketing for businesses in Brazil and abroad since 2000. Mário Moreno on LinkedIn