Google and HTTPS : Chrome Will Warn The Users to Not Protected Sites

Google is quite desperate regain their trust after PRISM Revelations. Google Chrome Browser Will Warn the Users to Visit Not Protected Sites. NSA Spyware Activities and the possible of relationship of Heartbleed vulnerability put Google in worser situation ever anything did to Google. Previously, Google AdSense behaved with the Publishers, particularly from India and China like marked thieves. Later Google strategically changed their attitude towards the publishers – all happened before Edward Snowden revealed the facts and his identity to the whole Internet users. Daddy like talks fully absent in Google’s current algorithmic update. Not abnormal, some European Countries already officially rejected to use Google Apps, Government of India, formally warned not to use Email Services from Microsoft, Google and other involved companies. HSTS was the actual need, however Google themselves do not have quite secure server. This is, somewhat the background of the entire story. Google Servers themselves do not follow their own declaration about SHA256 signature. However, this move of Google for their Chrome Browser is appreciable.

Google and HTTPS : Chrome Will Warn The Users to Not Protected Sites

Chrome could soon warn users about the absence of HTTPS and the risks of visiting a site free from this type of protection. Websites Not protect with HTTPS protocol could mean much more than a score slightly lower in rank in Google. The Mountain View giant, in fact, seems to have planned an update of the Chrome Web browser, which could alert users warning them about the risks of visiting a site is not protected by HTTPS.

The security team has proposed this type of update, with a final transition to this mode indication that should happen in 2015. This news has a capacity of no small importance, especially when you consider that about 50 percent of the market of all the browser is in the hands of Google Chrome. You might even think that, at worst, the sites are not protected by HTTPS could suffer halving of the traffic.

In fact, it is not clear how Google Chrome wants alert users if a screen like the one that currently indicates sites unsafe, though with a label displayed in the address bar like the ones currently indicate HTTPS security or otherwise.

The fact is that, many users may also decide not to visit the site which is not protected by HTTPS only because frightened of being advised of Google or why not aware of the significance of particular notice. This situation could damage all the sites that do not really have a need for security with HTTPS – we should not think of the personal blogs or simple information sites for the sake of sensitive data about the user. These too could suffer much more than a simple lowering of rank. These will also decrease the chance of using exact matched domains, broad matched domain and problems with limitations with IPv4 and also IPv6. Google, indeed is an example of using one domain for multiple purpose.

The Consequences of Forcing HTTPS on Chrome on the Competition Market

You can not be currently well aware of how it can affect the data traffic and above all, we can not predict the behavior of the other browsers. On the one hand, IE and Firefox might also decide to follow Google and, all together, forcing webmasters to implement HTTPS even on personal websites. On the other hand, competitors may decide to row against, trying to gain the approval of the webmaster, who, out of gratitude, might suggest to install Firefox or other browsers instead of Chrome.

To all this, you would add the question that Google might decide to add a label directly in the search engine to alert users that the site is not secure. In short, Google is pushing HTTPS taking the advantage of their popularity taking a big risk of loss of browser market share. Which is indeed, a need for Google to regain the trust from the corporate webmasters and corporate clients. Whoever is aware of the Governmental spyware activities will tend to use neutral country for hosting – Swiss Cloud is the excellent choice for saving business critical data.

On the other hand, webmasters are waiting to see how it varies depending on the rank of the absence of the HTTPS protocol, to see if it is really necessary to implement it on their own sites. This news along with the fact about HTTPS 2.0 could upset the plans.

To run even a small business, a License is required. One SSL/TLS certificate costs $10 / year. One domain name can even cost few hundred dollars per year (yeah, only .io costs $35/year, $10/year domain pricing is for the domains controlled by Verisign – dot com, dot net). The warnings will range from “Secure, but with minor errors” notice to “Affirmatively insecure” notice.