Skip to content

Browsing Chrome will prompt warnings for all websites containing text input fields as "Insecure" starting from October.

Starting from Chrome 62, released in October 2017, HTTP pages containing password or credit card input fields will be labeled as "Not secure." This applies to all HTTP websites with forms, such as blogs with comment sections or search boxes, and even pages visited in Incognito mode. As a...

All Google Chrome webpages featuring text boxes will be labelled "Insecure" starting October.
All Google Chrome webpages featuring text boxes will be labelled "Insecure" starting October.

Browsing Chrome will prompt warnings for all websites containing text input fields as "Insecure" starting from October.

In a move aimed at enhancing internet security and user protection, Google Chrome has started marking FTP (File Transfer Protocol) sites as "Not Secure" starting from Chrome 63, released in December 2017.

FTP, which has been in use since the 1970s, is unencrypted and vulnerable, making it susceptible to hacking and data breaches. The protocol transmits data—including passwords and files—in plain text, making it an easy target for eavesdropping and man-in-the-middle attacks on the network.

Google's decision to mark FTP sites as "Not Secure" serves as a warning to users that data sent or received over FTP can be intercepted or tampered with, posing security risks. This designation is crucial for website security as it encourages webmasters to adopt secure protocols such as HTTPS, which encrypts data and verifies the identity of the site, protecting user privacy and data integrity during transmission.

All HTTP sites with forms, including password or credit card fields, were marked as "Not Secure" starting from Chrome 62 in October 2017. This includes blogs with comments and search boxes. All HTTP pages visited in Incognito mode will also be marked "Not Secure" starting from Chrome 62.

Google's action will affect any certificate chaining to Symantec roots, except for the small number issued by the independently-operated and audited subordinate CAs. Google will remove trust in all Symantec's old SSL certificates in Chrome 70, to be released on Oct. 23, 2018.

HTTPS, short for "Secure," provides encryption for data transmitted over the internet. It is a more secure alternative to FTP and is used by popular websites such as Facebook, Messenger, Twitter, Pinterest, LinkedIn, Whatsapp, and Email.

In conclusion, Google Chrome 63 and later versions mark FTP sites as "Not Secure" to alert users to the lack of encryption and potential security risks inherent to the FTP protocol. This move promotes safer web browsing and website practices through encryption standards like HTTPS, ensuring a more secure and private internet experience for all users.

  1. To further bolster the security of online transactions, Google Chrome encourages the adoption of secure technology like HTTPS instead of the outdated and vulnerable FTP.
  2. The priority for cybersecurity in modern technology is reflected in Google Chrome's policy of marking FTP sites as "Not Secure," emphasizing the importance of secure protocols for safe web browsing.

Read also:

    Latest