I alluded to this issue in Re-evaluating the text of our Game Identification close reason.
At the time, the blog post was linked in the close reason itself - not a great look having a big security warning appear from a link on a close reason - so we removed it. I placed the contents of the blog into the Game Identification Wiki, to lessen the amount of clicks to the archived blog.
While it's not great that this cert issue still exists, for the time being I've edited the Game Identification Wiki, replacing the direct link to the blog with one from archive.org, which doesn't present the cert issue. When (if?) this cert issue ever gets solved, we can replace the link again to go directly to the blog.