Why is there an 'Â' after every sentence?

The UTF8 encoding of a non-breaking space (U+00A0) is 0xC2 0xA0. If you decode as ISO-8859-1 or CP-1252, that is 0xC2 (Â) and then NBSP (0xA0).

So the content is supposed to have an NBSP between the sentences, was encoded as UTF8, but declared as ISO-8859-1 or similar at some stage in its history. The page seems now to declare UTF8, so it's presumably had the wrong decoding reencoded as UTF8.

Because someone's messed up their encodings.Â

Which risk would TLS mitigate in this specific use case?

As with any http website, a malicious actor (e.g. someone in a coffee shop or an airport) could set up a plausible looking wifi service and then MITM the website and insert adverts or malware into the page.

However, that has been discussed on many other topics that are directly to do with TLS/certificates etc. so I don't think it's worth bringing up (aimed at the OP) every time there's an HTTP linked.

> I don't think it's worth bringing up (aimed at the OP) every time there's an HTTP linked.

Maybe rewritten it could be viewed as a warning for those who care instead of a criticism.

I guess nobody cares this days about being safe and secure. :(