4 ms·
It's probably more the other way around: the Chrome team only felt confident to show a "not secure" indicator, because so many domains are HTTPS now, and there
by Flimm 8y ago
It's probably more the other way around: the Chrome team only felt confident to show a "not secure" indicator, because so many domains are HTTPS now, and there is a good free option to get TLS certificates.