(It would be nice if we required a 'ssl.' subdomain be used for https-only connections, but nobody seems to like that suggestion, and there's some scaling

(It would be nice if we required a 'ssl.' subdomain be used for https-only connections, but nobody seems to like that suggestion, and there's some scaling issues) Fun fact: the .trust gTLD requires all connections to be made over HTTPS: https://www.nccgroupdomainservices.com/wp-content/uploads/2014/10/trust-technical-policy.pdf https://www.nccgroupdomainservices.com/wp-content/uploads/20... and this Langley post from july indicates that there's interest from chromium in enforcing that in the browser: (section 6.1) https://www.imperialviolet.org/2014/07/06/newtlds.html https://www.imperialviolet.org/2014/07/06/newtlds.html