All My GitHub Pages Are Marked as Dangerous — How Can I Fix This?

[StartTheImpossibleHX]

Select Topic Area

Question

Body

Hi everyone,

I noticed that all of my GitHub Pages sites are being flagged as dangerous or unsafe. I’ve searched the community and found some similar posts, but I’m not sure if their solutions apply to my situation.

Could anyone advise on how to resolve this issue or confirm whether those solutions are safe and suitable for me as well?

Thanks in advance for your help!

[mecodeatlas]

Hey @StartTheImpossibleHX! Thanks for reaching out! 👋

I noticed that this same issue has been brought up in other discussions recently. In general, this type of warning is more closely related to the browser (often Chrome) than to GitHub Pages itself.

That said, I’m sharing two discussions below that describe almost exactly the same problem — and both have already been addressed. Hope they help:

• My GitHub pages is getting marked as Dangerous by Chrome
• My all deployment pages in github are marked as dangerous sites.. but they are just simple projects like calculator and my portfolio etc

If possible, try accessing your site through other browsers to see if the warning still appears. Let us know if the issue persists!

[Hariprashad-Ravikumar]

Why it happens
Your *.github.io sites are being blocked by Google Safe Browsing, not by GitHub. 99 % of the time this happens when a Pages site contains a template or “clone” that looks like a well-known login page (Netflix, Facebook, Instagram, etc.). Safe Browsing automatically tags that as potential phishing — and every other site under the same account inherits the warning.

Fix it step-by-step

1. Remove or clearly change any look-alike pages (logo, colors and real login fields are the usual triggers).

2. Serve everything over HTTPS

   • Repo ➜ Settings → Pages ➜ tick Enforce HTTPS.

3. Check your status – run every URL through the Google Safe Browsing checker:

4. Request a review

   • Add each site (or a wildcard like https://your-username.github.io/*) to Google Search Console.
   • After ownership verification, click Security & Manual Actions → Security Issues → Request Review. Google usually replies in 24-48 h once the risky content is gone.

5. Be patient – the warning can linger for a few hours after Google lifts the flag while browser caches expire.

Can GitHub Support fix it? Unfortunately no; the blocklist lives entirely on Google’s side, so the Search Console review is the only reliable route.

Is it safe to follow these steps? Yes — you’re just verifying ownership and asking Google to re-scan your cleaned-up site. Nothing else about your account changes.

Good luck, and hope your Pages go back to normal quickly!

[tanvirjoy04]

Google Search Console works. Point no 4
Link:
http://search.google.com/search-console/

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬