Most of the online traffic is now sent over an HTTPS connection, making it "secure". In fact, Google warns that unencrypted HTTP sites are "not secure." So why is there so much malware, phishing and other dangerous online activities?
"Safe" sites have only one secure connection
Chrome was used to display the word "Safe" and a green padlock in the address bar when you visit a website using HTTPS. Modern versions of Chrome Simple have a small gray lock icon without the word "Secure".
This is partly because HTTPS is now considered a new standard for the baseline. By default, everything should be secure, so Chrome only warns you that a connection is "not secure" when you access a Web site through an HTTP connection.
However, the word "safe" is also gone because it was a bit misleading. It sounds like Chrome is responsible for the content of the site, as if everything on this site were "safe". But that's not true at all. A "secure" HTTPS site might be malware-filled or a phishing phishing site.
RELATED: Why does Google Chrome say websites are "not safe"?
HTTPS stops snooping and tampering 
HTTPS is great, but not only does it make sure. HTTPS stands for Hypertext Transfer Protocol Secure. It's like the standard HTTP protocol for connecting to websites, but with a layer of secure encryption.
This encryption prevents people from spying on your data during transmission and prevents man-in-the-middle attacks that can alter the site as it is sent to you. For example, no one can look at the payment details you send to the site.
In short, HTTPS ensures that the connection between you and this particular website is secure. Nobody can overhear or manipulate him. That was it.
CONNECTED: What is HTTPS and why should I do that?
This does not really mean that a site is "safe"
HTTPS is great, and all sites should use it. All it means is that you use a secure connection with this particular website. The word "safe" does not say anything about the content of this site. It just means that the website owner has purchased a certificate and set up encryption to secure the connection.
For example, a malicious website full of malicious downloads can be deployed over HTTPS. This means that the website and the downloaded files are sent over a secure connection, but they may not be secure.
Similarly, a criminal could buy a domain such as "bankoamerica.com" to obtain an SSL encryption certificate and mimic Bank of America's real Web site. This would be a "safe" padlock phishing site, but that means you have a secure connection to this phishing site.
HTTPS is Still Big
Despite the phrasing that browsers have been using for years, there are no HTTPS sites. It's not really "safe". Websites that migrate to HTTPS help solve some issues, but do not stop malware, phishing, spam, vulnerable site attacks, or other online scams.
Moving to HTTPs is still great for the internet! According to Google's statistics, 80% of the web pages loaded in Chrome on Windows are loaded via HTTPS. And Chrome users on Windows spend 88% of their surfing time on HTTPS sites.
This transition makes it more difficult for criminals to eavesdrop on personal information, especially on public WiFi or other public networks. The likelihood that you will encounter a man-in-the-middle attack on public Wi-Fi or another network will be significantly reduced.
For example, suppose you download a program's .exe file from a website You are connected to a public Wi-Fi network. If you are connected to HTTP, the Wi-Fi operator could manipulate the download and send you another malicious EXE file. When connected to HTTPS, the connection is secure and nobody can manipulate your software download.
That's a big win! But it is not a silver bullet. You still need to use basic online security methods to protect against malware, detect phishing sites, and avoid other online issues.
Credit: Eny Setiyowati / Shutterstock.com.