I was doing a video on how HTTP Strict Transport Security protects you from Man-In-The-Middle attacks and was using Google as an example. Turns out google.com isn't in the HSTS preload list, and just redirects to www.google.com which means HSTS is only set for www.google.com, not google.com 1/2
Comments
Interesting. It doesn’t look good.
I know a lot of people de-googling because of their “AI” goals. So this could be a problem in the future as people may utilize Google again.
When you’re in a captive portal, but not one that pops the special UI. Often folks (myself) type “google.com” into the address bar. The captive portal can actually serve up its page here. Not really a great reason, but I can understand it being a legacy decision.
I think any OS/browser that prompts you to go to a captive portal implements that feature themselves by trying to load an unencrypted "connectivity check" page.
When that fails, I usually use https://example.com.