Android versions prior to 4.4 support only TLS 1.0 which is deprecated and many old devices aren't upgradable. The same for Mobile IE 10.

IE 10 in Windows Server 2008 doesn't support TLS 1.1+ by default.

Yup, my last phone upgrade was prompted by this.

But the old phone is significantly better at making actual phone calls than the new one.

Why is it your job to police the browsers people use?

> Must be decades old.

So? If they still power on and are capable of talking HTTP over a network, and you don't require the transfer of data that needs to be secured, why shouldn't you "let" them online?

I don't know about you, but I'd rather my ancient laptop not end up as part of a botnet simply because I visited the wrong website with it.

Why you shouldn’t use old, unpatched software on an open network that doesn’t support modern protocols?

Beats me.

Usually browsers on hobbyist legacy operating systems, to which modern browsers haven’t or can’t be ported, not to mention keeping root certificates up to date. Or even if they do support SSL, then only older algorithms and older versions of the protocol. It’s nice to still be able to browse at least part of the web with those.

The problem is usually SSL support, the problem is that older SSL and TLS versions are being disabled.

I actually have an example myself - an iPad 3. Apple didn't allow anyone else than themselves to provide a web browser engine, and at some point they deliberately stopped updates. This site used to work, until some months ago. I currently use it for e-books, if that wasn't the case I think it by now it would essentially be software bricked.

I acknowledge that owning older Apple hardware is dumb. I didn't pay for it, though.