Where did you get that link? Was it one of the sample links? I don't think those are real links. But if you type in https://facebook.com and click "Make it look dodgy" it will give you a real link.

http://hey.look.a.verylegit.link/malware-425iphone)ip-steale...(.docx.html.rar

Edit: Although it appears Hacker News decided to mangle this link that I posted. Apparently it's not happy about mismatched parenthesis in links. Why HN wants to try to match parenthesis in links... that's a good question.

Markdown uses parenthesis? HN software parses markdown in comments to format them?

HN doesn't use Markdown, it has its own eccentric and much more limited markup system.

I get this in Firefox 55:

http://megg.ml/i/771715c9c2445b972e07fa529c6fdb4a.PNG

Note the second line, "The connection to irc.verylegit.link was interrupted while the page was loading." Does that show up for you?

Yes, I found that, but that's not even an inadequate error message -- it's just wrong. Firefox has no way to tell if the connection is encrypted or not because the connection is being dropped while the encryption is being established.

So a connection that doesn't exist cam hardly be encrypted now can it? Scnr

But yeah I noticed this trend too in browsers, it's getting harder to get to the technical bits every time they try to make these warnings more user friendly. I usually switch to openssl s_client in a terminal at this point.

Complain about how hard it is to get to the details of a bad cert if you want, but this instance does not exemplify the trend you're referring to.

This is one of only HTTPS errors that you aren't required to click through to uncover the details of the error—the connection is being shut down.

Show that it decreases conversions and then maybe people will stop doing it