UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.62 Safari/537.36

Steps to reproduce the problem:
This is a feature request!

What is the expected behavior?
The user enters a url or domain in the address bar and the browser tries it as https first.

If it fails it should ask the user what to do, load the page anyway (un-securely) or abort loading the page.

This feature should be introduced in stages, initially default to off but let users enable "Try HTTPS first if protocol not specified". Later releases should default to enabled but allow the user to turn the feature off.

What went wrong?
Currently the browser tries the request as http. Unless the domain happens to be in the HSTS preload list a MITM attack could provide a fake site to the browser and user.

Did this work before? N/A 

Chrome version: 62.0.3202.62  Channel: stable
OS Version: 10.0
Flash Version: 

Started out as a discussion in the comments on https://www.troyhunt.com/the-6-step-happy-path-to-https

The HSTS preload list can not continue to grow indefinitely to hold all sites in the world. Ideally a HSTS DNS record should be provided via DNSSEC which would make this feature request obsolete, but that is unlikely to happen anytime soon.