Google has announced that its Upcoming chrome browser will automatically divert half-finished URLs to HTTPS pages.
Google Chrome previously load a domain via HTTP by default when you typed an incomplete URL (say, PPCexpo.com) into the search engine.

The fact, as mentioned above, has been in practice for those who don’t have time to type the entire URL with the proper protocol.
That’s changing soon with a new update that Google is rolling out as part of Chrome 90.
The giant search engine brand has announced that Chrome will use the more secure HTTPS by default when you type a URL without specifying a protocol in the Omnibox, assuming the site you’re visiting already supports HTTPS.
The new default will apply to the browser’s desktop and Android versions. It is also rolling out to Chrome on iOS soon.
On its blog, Google said the following:
“Starting in version 90, Chrome’s address bar will use https:// by default, improving privacy and even loading speed for users visiting websites that support HTTPS. Chrome users who navigate to websites by manually typing a URL often don’t include “http://” or “https://.” For example, users often type “example.com” instead of “https://example.com” in the address bar.
In this case, if it was a user’s first visit to a website, Chrome would previously choose http:// as the default protocol1. This was a practical default in the past when much of the web did not support HTTPS.
Chrome will now default to HTTPS for most typed navigations that don’t specify a protocol2. HTTPS is the more secure and most widely used scheme in Chrome on all major platforms.
In addition to being clear security and privacy improvement, this change improves the initial loading speed of sites that support HTTPS, since Chrome will connect directly to the HTTPS endpoint without needing to be redirected from http:// to https://.
For sites that don’t yet support HTTPS, Chrome will fall back to HTTP when the HTTPS attempt fails (including when there are certificate errors, such as name mismatch or untrusted self-signed certificate, or connection errors, such as DNS resolution failure).
This change is rolling out initially on Chrome Desktop and Chrome for Android in version 90, with a release for Chrome on iOS following soon after.”
If a site doesn’t support HTTPS yet, the browser will switch to HTTP instead. This will also occur in the event of certificate errors or connection issues.
The protocol encrypts any information transmitted over a network to fend off potential attacks.
Of course, Google will still alert you to the risks of visiting HTTP websites.
HTTPS protects users by encrypting traffic sent over the network so that sensitive information users enter on websites cannot be intercepted or modified by attackers or eavesdroppers.
Google concluded by saying:
“Chrome is invested in ensuring that HTTPS is the default protocol for the web, and this change is one more step towards ensuring Chrome always uses secure connections by default.”
What are your thoughts on Google’s move?
We will help your ad reach the right person, at the right time
Related articles