As noted on NeverSSL:
> [...] it [...] means that if you're relying on poorly-behaved wifi networks, it can be hard to get online. Secure browsers and websites using https make it impossible for those wifi networks to send you to a login or payment page. Basically, those networks can't tap into your connection just like attackers can't. Modern browsers are so good that they can remember when a website supports encryption and even if you type in the website name, they'll use https.
I usually use gstatic.com, which does redirect, but also gstatic.com/generate_204 is Chrome's own capive portal test page and does not redirect. There's also msftncsi.com, which (/ncsi.txt) is Microsoft's test page.
http://money.cnn.com/2016/09/08/technology/google-chrome-fla...
And, despite money.cnn.com being one of the Subject Alt Names on their certificate (as well as plenty of app, api and some staging domain names), that domain in particular rejects connections to port 443.
Maybe their transition is incomplete and they're not ready to announce yet?
Funny how many people independently ended up in that same situation. How did y'all start?
