As a security company, anything less than "Full (Strict)" should not exist.
3,736 karma · joined April 1, 2014
[ my public key: https://keybase.io/r1ch; my proof: https://keybase.io/r1ch/sigs/pcrLB7IUV_tZ-u-B7hUSOD-5ke3L2JSthNhI1izUmI4 ]
As a security company, anything less than "Full (Strict)" should not exist.
Browsers generally do a good job of ensuring HTTPS these days, but still you should pay attention to make sure you're on HTTPS when using public Wi-Fi.
To the less experienced sysadmin everything looks like it's working fine and users also don't notice any difference, which is why it's a terrible default.
Sure you _can_ configure Cloudflare securely, but it should be secure out of the box. But that adds friction when the origin doesn't have a valid SSL certificate which probably hurts someone's KPIs.
It's hard to take Cloudflare's commitment to security seriously when they still ship such terrible default settings.