This is wrong. Lack of HTTPS does not result in a deceptive site warning...

@forest No, chrome may also be showing this error for http sites: Link. "Website traffic is not redirected to HTTPS"

It doesn't show it for all non-HTTPS sites of course, otherwise the web would be broken.

So? That doesn't change the fact that this issue might be due to the fact that it's http instead of https. I don't get why this answer is downvoted, it might be helpful for other users...

You can test this by visiting neverssl.com. Does it show the warning?

No, I never said that all http sites would show it, but this issue can also occur when a site does not redirect the website from HTTP to HTTPS.

Then what determines it, if not the domain name? neverssl.com does not redirect to HTTPS, so why would it not throw the warning, but OP's example would? Also, the HTTP link he provided works over TLS, so perhaps OP could check if the issue still occurs if he manually loads the HTTPS version.

This is the reference I found. Are you sure that these references are wrong?

That reference is very vague. I take "the website carries malware or threat files" to include phishing indicators. And traffic not being redirected to HTTPS is clearly not sufficient to trigger the warning on its own.

Do you have a browser that can test this?

From support.google.com/chrome/answer/99020:

> Deceptive site ahead: The site you're trying to visit might be a phishing site.

Yes I found this blog entry from Google as well which is a little contradicting the claim that the error can show up if the SSL certificate is not installed correctly... I will remove my answer if you're sure that the other reference is wrong, let me know :)

I'm not 100% sure and I'm still looking it up to double check.

It could be a combination of multiple factors.

@AleksanderRas From mootmoot's answer: transparencyreport.google.com/safe-browsing/…

I imagine Google is using some proprietary heuristics to detect this.

Okay, I get it now, I will remove my answer.