Sanity: http:// hosts must have working https:// counterparts

[Darkspirit]

https://www.hardenize.com/report/sparkasse-hannover.de/1563935842#www_https

Test passed
Everything seems to be well configured. Well done.

URL: https://sparkasse-hannover.de/
Analysis: HTTP connection failed

sparkasse-hannover.de responds on port 80, but not on port 443.
As long this is the case, browsers can't safely default to https.
Opening sparkasse-hannover.de fails with https://addons.mozilla.org/en-US/firefox/addon/https-already/ and also with Desktop Servo.

• If https://host fails while http://host works, HTTPS should be orange or red and error message should explain that http:// hosts need to offer https:// as well.
• If https://host fails while https://www.host works, HTTPS should be orange or red and error message should explain that users often type in domains without www. (Chrome even hides www, so users can't necessarily notice the difference.)

[Darkspirit]

(Chrome even hides www, so users can't necessarily notice the difference.)

https://bugs.chromium.org/p/chromium/issues/detail?id=883038#c114

For several months, we’ve had this version enabled in our Canary, Dev and Beta channels and are confident that it is ready to be enabled in the Stable channel as well.

[Darkspirit]

https://twitter.com/estark37/status/1160942611521105920