> I used to test with http://neverssl.com/ until they added HTTPS for some reason.

My first reaction was along the lines of "What? That can't possibly be right..."

After testing a bit, it looks like you can load https://neverssl.com but it'll just redirect you to a non-https subdomain. OTOH, if the initial load before redirecting is HTTPS then it shouldn't work on hotel wifi or whatever, so still seems like it defeats the purpose.

Huh.

neverssl added an HTTPS version for browsers that automatically connect to HTTPS when entering a domain name (like Chrome probably will after this change, eventually). The HTTPS version of the site uses Javascript to load a random http:// subdomain of neverssl.com so automatic HTTPS redirects are still defeated.

http.rip will probably show a "website unavailable" error at some point unless you manually type in the http:// prefix.

IANA's http://example.com still has a plain http version.