Google Safe Browsing Warning on Staff Login Page

Website URL

https://sritesepattendance.xo.je/staff/login.php

Error Message

Google Chrome displays a red “Dangerous site” warning when accessing the Staff Login page.

Google Search Console reports:

The main website, Student Login and Administrator Login work normally in Chrome.

Other Information

Hello InfinityFree Support Team,

Our educational institution operates the SRITE School Experience Program attendance portal.

Google Safe Browsing has flagged our Staff Login page as deceptive, although the Student and Administrator login pages work normally.

We have performed the following checks:

  1. Reviewed the Staff Login PHP file and related configuration files. No obvious malicious scripts were identified.
  2. Checked the hosting File Manager. No unfamiliar files were found.
  3. Tested all login URLs using PowerShell. They returned HTTP 200 without HTTP redirects.
  4. Found that Student, Staff and Administrator login URLs initially return a JavaScript cookie verification challenge containing slowAES.decrypt.

Could you please investigate whether the hosting-level browser verification system or another hosting-related issue could be contributing to the Google Safe Browsing warning?

We would appreciate guidance on resolving the issue safely without disrupting the existing portal.

Thank you.

Sri Ram Institute of Teacher Education
New Delhi, India

Beep boop, I’m a bot! I dug through the forum to get you started. I sometimes get things wrong though, so do with this what you will until a human has a look.

Google decides this listing, not our hosting, and we can’t remove it for you. Only Google can lift it, after you request a review in Search Console. The article below explains what the warning means and how to get it removed.

This article covers your exact warning:

Its list of causes doesn’t include the cookie verification challenge you found, so it doesn’t point to that as a reason for the flag. The article says Safe Browsing judges what a site looks like. Two of its listed causes fit a school attendance portal:

  • The site asks visitors to log in on behalf of an organization without making that relationship clear.
  • The site uses another organization’s name or branding.

For a legitimate site, the article suggests these changes:

  • Put a public homepage with real content in front of the login forms.
  • Say clearly who runs the site, with an about page and contact details.
  • Say that it’s run for your institution, and add a privacy policy if you collect user data.
  • Use your own branding only.

Once that’s in place, use Request review in the Security Issues report. In the review, explain what the portal is, who runs it and what the staff login is for. The article says to request a review only once, and only after everything is fixed.

One question could narrow this down: does the Staff Login page use any name, logo or design from another organization, or look different from the Student and Administrator pages? Something there would be the first thing to check, since only that page was flagged.