User talk:Eighty5cacao/misc/List of CDNs by HTTPS support

What does SNI change?
"HTTPS support on custom domain names almost always requires a premium account."

Mention of "buckets" in a recent Cyanide & Happiness comic brought this to mind. Since you wrote this comparison, Internet Explorer on Windows XP reached end of support in April 2014. IE on XP was the last major web browser not to support Server Name Indication, and it's a lot easier to offer HTTPS at no extra charge. In addition, an automated gratis certificate authority called Let's Encrypt has since gone live, and a major search engine has slightly boosted ranking of documents on secure origins. So in the era of SNI, ACME, and SEO bonuses, are high-performance static file hosting services and CDNs still charging extra for HTTPS? --Tepples (talk) 16:16, 20 November 2017 (UTC)
 * Obviously this page is very unmaintained, to the point where I could almost request its deletion and start over. I'm not intending to put much more thought into it. But your question could be answered at least partially with "no," because I know in particular that Cloudflare has for a few years now supported HTTPS on custom domain names even for free accounts. (Cloudflare has always supported only custom domains, HTTPS or no; it does not provide any "shared" domains for use as public-facing websites. The gratis HTTPS feature continues to require SNI, and upload of custom certificates still requires one of the higher paid tiers, but this isn't relevant for the reasons you just explained.) --Eighty5cacao (talk) 02:06, 21 November 2017 (UTC) (+ 04:41, 21 November 2017 (UTC))