That's not the issue. Example.com is just distinctive for supporting both http and https, whereas modern sites redirect you to the https version. Chrome remembe

That's not the issue. Example.com is just distinctive for supporting both http and https, whereas modern sites redirect you to the https version. Chrome remembers which domains support https (which is nearly all of them) for when the domain is typed naked, and apparently won't fall back to http if it recalls https working in the past. So, until now, domains like "example.com" would sometimes let you get to an airplane's login page when domains like "facebook.com" wouldn't.