Sharing is caring!

Almost three months ago, Google has promised that starting January 2017, Google will mark HTTP websites as “not secure”. It seems that this is already happening, as the Chrome 56 beta is warning users that some HTTP connections are insecure. The warning appears large in the left corner of the browser’s URL bar to draw user’s attention, but it’s not brightly colored to disturb him/her.

Google will release the stable version of Chrome next month, and it will include the said warning. The update will roll out first for desktop computers, then the Android version of Chrome will follow.

Until now, the Android version has highlighted only HTTPS websites, and soon, insecure HTTP websites will be also highlighted.

The guys at Google have explained that the “not secure” warning will be reserved for non-encrypted websites that collect personal information such as passwords, credit card numbers or addresses, so that users will stay away from them and never visit them again. The label won’t appear every time a user will visit a HTTP site, as there are many harmless pages that have no interest in collecting such information.

Google had in mind to mark all non-encrypted sites as insecure for a long time, but last year, the UI changes had to be dropped because webmasters needed time to transition their websites to an encrypted format.

Chrome 56 beta brings more changes to the table, such as Web Bluetooth support, which allows websites to connect to other devices via Bluetooth, but developers will need to use some simple JavaScript code in order to implement the feature. The new beta of the browser also comes with a new CSS command, “position: sticky”, which allows developers to keep website elements to a fixed position.

Google has also added a new Remote Playback API and WebVR API for Android and improved the functionality of the Image Capture origin trial. Chrome 56 beta may come with glitches, but the developers will fix them before they will release the stable version of the browser.