In short. The "Not secure" label in front of your website's address, in Chrome or Safari, appears when the site does not use a valid secure connection (HTTPS, the padlock), either because it has no certificate or because the certificate is invalid. Your visitors see this warning and may become wary and leave, especially before entering personal information. It is up to you, or to your hosting provider or web provider, to install the certificate and redirect every address to the secure version. Usually allow a few minutes of configuration.
"Not secure" appears in front of the address when the page is loaded without a valid encrypted connection: the site is served over http:// instead of https://, or its HTTPS certificate is not valid. To make it disappear: install a certificate, serve the site over HTTPS, then redirect every http:// address to https://.
Last verified: November 18, 2026, in the Chromium source code and in Apple's Safari guide.
What your visitors see
- Chrome shows "Not secure" next to the icon, at the start of the address bar. According to the description of this text in the Chromium code, it flags an unencrypted (HTTP) site or an invalid HTTPS connection.
- Safari: according to Apple's guide, "the words “Not Secure” appear in the Smart Search field" when the site does not use HTTPS with a valid certificate. Apple advises against entering personal or banking information there.
Unlike "Your connection is not private", the page displays: nothing is blocked. But the words are visible on every visit, and a visitor hesitates to fill in a form or pay on a site marked "Not secure".
Step 1: find out why
Run our free SSL certificate check on your domain.
- No certificate, or HTTPS does not answer: the site was never moved to HTTPS. Go to step 2.
- Certificate present but in error (expired, wrong name, not trusted): the browser usually blocks the page with a full-screen warning. See "Your connection is not private".
- Valid certificate, but "Not secure" displayed: you are on the
http://address, with no redirect. Go to step 3.
Step 2: enable HTTPS
- Shared hosting: enable the free certificate offered by the host (often Let's Encrypt) for the domain, with and without
www. - Server you manage: get a certificate with an ACME client such as certbot, then configure the web server to listen on HTTPS (port 443).
- Site builder or hosted CMS: the option is usually in the domain settings ("HTTPS", "SSL").
Step 3: redirect HTTP to HTTPS
As long as the http:// address stays reachable without a redirect, visitors who use it (old links, bookmarks, manual typing) see "Not secure".
- Add a permanent (301) redirect from
http://tohttps://, for all pages. Many hosts offer a "Force HTTPS" checkbox. - In the CMS, replace the site address with the
https://version (in WordPress: Settings > General). - Once everything is checked, send the HSTS header: the browser will then go straight to HTTPS. Our free security headers check shows the line to add.
Step 4: check
- Open
http://your-domain.com: you should land onhttps://your-domain.com, without "Not secure". - Also test
http://www.your-domain.comand your public subdomains.
Check your domain for free. AttackScout checks your certificate, the redirect to HTTPS and the HSTS header, from the Internet, in one minute, with no account. Check my domain
Frequently asked questions
My site has no form. Do I need HTTPS?
Yes. Chrome and Safari show "Not secure" on any HTTP page, with or without a form. And without encryption, a page can be altered along the way on a public network.
The certificate is installed, but "Not secure" still shows on some pages.
Check the address: you may be on an http:// page that is not redirected. Add the redirect for the whole site.
Does moving to HTTPS lose search ranking?
A clean 301 redirect passes pages on to their HTTPS addresses. Keep the same paths and redirect each old address to its new version.
Sources
Accessed on 11/18/2026.
- Chromium,
IDS_NOT_SECURE_VERBOSE_STATEand its description (components/omnibox_strings.grdp), English text "Not secure": https://github.com/chromium/chromium/tree/main/components - Apple, Avoid fraud by using encrypted websites in Safari on Mac: https://support.apple.com/en-us/guide/safari/sfri40697/mac
- Certbot, documentation: https://eff-certbot.readthedocs.io/en/stable/using.html