Skip to main content
MANIFOLD
When will Chrome first require manual confirmation to open a non-https website?
17
Ṁ585Ṁ3.6k
2030
0.5%
2023
0.8%
2024
1.3%
2025
87%
2026
4%
2027
2%
2028
2%
2028
1.4%
2029
1%
2030 or later

Resolves to the year a normal user running the default installation of Google Chrome first needs to take additional actions (confirmation dialog, option change etc.) before seeing the contents of a website that is not using https.

Get
Ṁ1,000
to start trading!
Sort by:

Chrome 154 is out, which is supposed to be the version that enables this by default: https://developer.chrome.com/release-notes/154#ask_before_http_on_by_default

However, I wasn't able to confirm this on Linux. (It only gives the warning in Incognito, which I believe has been in place for some time.) I tried to make sure this was a fresh installation of the browser and deleted the directory containing my user data. Is anyone else able to confirm this, perhaps on a different operating system?

@CollectedOverSpread I was able to confirm it on Windows.

bought Ṁ300 YES

https://blog.google/security/https-by-defau/

One year from now, with the release of Chrome 154 in October 2026, we will change the default settings of Chrome to enable “Always Use Secure Connections”. This means Chrome will ask for the user's permission before the first access to any public site without HTTPS.

bought Ṁ5 NO

For y'all's convenience:

http://example.com

It currently does only if Advanced Protection Programme is enabled on the account.