There has been a bypassable error for TLS 1.0 and 1.1 for several months. There have been error messages in devtools. In October of 2018 the browser vendors jointly announced that this change was coming. [1][2] This is happening in coordination with Chrome. The sites that are affected by this have had nearly 2 years to sort out their upgrade to TLS 1.2 or 1.3.
> The sites that are affected by this have had nearly 2 years to sort out their upgrade to TLS 1.2 or 1.3.
... or are hardware appliances with a management interface, segregated on an internal VLAN, that will never be updated, but which were helpfully "forward thinking" enough to force HTTPS.
... or are hardware appliances with a management interface, segregated on an internal VLAN, that will never be updated, but which were helpfully "forward thinking" enough to force HTTPS.