(please share the FULL error message you see, if applicable)
Beware of fraudulent sites
Attackers on [MY WEBSITE] can trick users into dangerous actions, such as installing software or disclosing personal information (such as passwords, phone numbers, or credit cards).
(Chrome Safe Browsing)
Other Information
(other information and details relevant to your question)
This is a website to start my new business and I already reported this problem to google domain. The response was negative. I wonder if there’s a critical issues in my php source code. I am starter programmer so I hope I can learn from you guys about this warn. Reminder, my website is for my business not phishing.
It’s just an issue with Google Chrome. It has a long history of flagging the wrong sites as phishing and not flagging the ones who were phishing. My advice: don’t use chrome. It works good (the site) on other browsers
This could happen with Chrome if you are using PHP to get visitors IP addresses or for a few other reasons. A few years ago, I had the same issue, but I fixed it by improving my code logic.
I am so glad you to let me know that. However, I don’t use any function that use clients ip address. But I would like to check it again. Thank you for helping me.
I checked it again, and I guess I found 3 reasons can be the issue.
First, I use session system to login.
Second, I use $USERDATA value to save the login data which can be very suspicious to google chrome (probably not because it’s backend)
Third, MAYBE MAYBE MAYBE, does my source code or my domain infected by malicious software?
Oh I just bought on free plan in infinityfree website. the sub domain one.
Okay so first time I registered with .wuaze.com and then I added subdomain on it and I removed the first one.
Also, I detected an additional issue; I registered out of curiosity and it just shown a blank page, also when I tried to login with the password and the id it didn’t work.
I think you should add the following lines at the beginning of the script so we can see what’s the problem here more clearly (and this might help you diagnose more errors): error_reporting(E_ALL);
ini_set(‘display_errors’, ‘1’);