Your browser shows Not Secure when a website is loading over a plain, unencrypted connection (HTTP) instead of an encrypted one (HTTPS). It means anything you type on that page, such as passwords or card numbers, could be read or changed by others on the network. It is a warning about the connection, not proof the site is dangerous, but you should avoid entering sensitive details.
Why this happens
- The site uses HTTP, not HTTPS. Browsers now label every unencrypted site as Not Secure. If the site never set up a security certificate, every page shows the warning.
- An expired or invalid certificate. If a site's certificate has expired or does not match its address, the browser distrusts it. This often shows a stronger full page warning rather than just the label.
- Mixed content. A page loaded securely but pulls some parts, such as images or scripts, over an insecure connection, so the browser downgrades the label.
- A wrong device clock. If your computer or phone has the wrong date, valid certificates can look expired, triggering security warnings.
- Network interference. On some public or monitored networks, traffic is intercepted, which can cause certificate warnings.
Is this normal?
Seeing Not Secure on an old site that never adopted HTTPS is normal, since most of the web is now encrypted and those sites stand out. A full page certificate warning on a well known site is not normal and deserves caution.
Does it cause any problems?
On a Not Secure page, information you send is not protected and could be intercepted or altered, which is a real risk for logins and payments. Just reading a page is lower risk, but you should never enter passwords, card details, or personal data on a Not Secure connection.
How to fix or check it
- Do not enter passwords, card numbers, or personal details on a page marked Not Secure.
- Check whether a secure version exists: try changing the address from http to https, or look for the site's official secure link.
- Confirm your device date and time are correct and set to automatic, since a wrong clock causes false certificate warnings across many sites.
- Reload the page and clear the browser cache, in case an old insecure version was cached.
- Avoid sensitive actions on public wifi, where interception is more likely, and consider a trusted VPN for such networks.
- If you see a full page "connection is not private" or expired certificate warning on a major site, do not bypass it, since the certificate is genuinely invalid or being intercepted.
- If it is your own website, install a valid security certificate, redirect all HTTP traffic to HTTPS, and fix any mixed content so pages load fully over HTTPS.
Frequently asked questions
Does Not Secure mean the site has a virus?
No. It means the connection is not encrypted, so data you send is not protected. The site itself may be perfectly legitimate, but you should still avoid entering sensitive information on it.
Is it safe to just read a Not Secure site?
Reading a page is lower risk than submitting data, since the danger is mainly to information you send. Avoid logging in, entering payment details, or filling personal forms while the page shows Not Secure.
Why does one site show Not Secure while others do not?
Because that site has not set up encryption while the others have, or it has a certificate problem. The label reflects each site's own security setup, not your browser or device being at fault.