Public hostnames get marked phishing suspicious by Chrome


I am using a Zero Trust tunnel. I have made some of my locally available applications accessible via the public hostnames feature that zero trust tunnels offer.

I have seen now that after one day of usage some of these hostnames got declared as phishing suspicious by Chrome. Did I do something wrong?
The applications require a Google authentication and directly after the authentication happens and I’m get redirected to the hostname I’m getting the red flag shown in Chrome.

Did someone else also experience this one?

Thank you very much!

1 Like

Yes, I am seeing the same behavior. I am not sure if the reason is the domain I am using is brand new or if there is another reason. I am able to proceed and connect through the tunnel, but am also curious if this is expected behavior.

1 Like

Same here :frowning: Using Github as an IdP however