3 ms·
They do have SSL on the website, but it's optional. But assuming MITM, the only defense against MITM a site owner has is getting preloaded on the HSTS list. Ref
by toast0 3y ago
They do have SSL on the website, but it's optional. But assuming MITM, the only defense against MITM a site owner has is getting preloaded on the HSTS list. Refusing to serve content in HTTP doesn't help, because the MITM can upgrade the request on the backend. Redirecting from HTTP to HTTPS is window dressing.
For a site like this, I might version sniff and send modern browsers to a favicon served over HTTPS with HSTS headers; future accesses will get upgraded to HTTPS (unless the MITM drops these requests), and older browsers don't understand HSTS anyway. But I wouldn't put that favicon on generally, because it's not likely possible to get a certificate older browsers will like, and older browsers like to throw popups when they can't negotiate https on subresoures, which ruins everyone's day.
Older browsers are likely to require SHA1 certificates, and have a more limited selection of CAs. CA/Browser rules prohibit issuing new SHA-1 certificates, so you're pretty much out of luck there. Even if you can get a SHA-1 certificate that older browsers like, you have to also have a certificate that newer browsers like and get your server to distinguish between the two and serve the right certificate. Helpfully, Client Hello does not provide user-agent information, so you have to kind of guess at age of the browser / capability by what version, ciphers, and extensions they suggest. But really, all of that is moot unless you can get a trusted CA to issue a usable cert, which I'm pretty sure you can't.