> The issue this warning is calling out is that someone who controls the certificate could modify the data No, the issue the warning is calling out is that the

> The issue this warning is calling out is that someone who controls the certificate could modify the data No, the issue the warning is calling out is that the server your browser is communicating with can't prove that it's yamanote.style. There's no way to determine whether this is misconfiguration or fraud (though you can apply logic and usually come to the conclusion that it's misconfiguration in this case). Example attack: 1. I host a fraudulent site on GitHub Pages, so it gets served up with the *.github.com cert. 2. I intercept your request to yamanote.style (let's say you're on my network [let's say I'm China]) and send you my GitHub pages content, signed by GitHub with their *.github.com cert. This would look just like what's happening to yamanote.style right now, except that I would be controlling the content of yamanote.style.