GitHub Pages site always flagged as "Deceptive site ahead" / Safe Browsing warning — account/subdomain suspected

[sepidehghaderi7]

Select Topic Area

Question

Body

Hello GitHub team and community,

I'm seeing a persistent browser Safe Browsing / "Deceptive site ahead" (phishing/malware) warning for every GitHub Pages site I create under my account. This happens even for brand-new repositories that contain only a simple "Hello World" HTML page.

Details:

• Example repo: https://github.com/saniyamujawar04/Netflix-clone
• Example Pages URL: https://saniyamujawar04.github.io/Netflix-clone/
• I created fresh repositories, used main branch with /root, cleared caches, disabled custom domains — nothing helps.
• The same files deployed from another GitHub account (my brother’s) work fine with no warnings.
• Issue reproduces across multiple devices and networks.

Steps I took:

1. Created several new public repos with only static HTML.
2. Enabled Pages (main /root), waited for deployment.
3. Tested on other devices/networks, cleared browser cache.
4. Created a brand new GitHub account and repeated — same result.

Hypothesis:
I suspect the GitHub Pages subdomain (username.github.io) or my account is listed in a third-party blocklist (e.g. Google Safe Browsing, Microsoft SmartScreen) from a prior classification, and that reputation is causing Safe Browsing to flag the Pages site regardless of current content.

What I need help with:

1. Can GitHub confirm whether saniyamujawar04.github.io (and subpaths) are flagged on GitHub’s side or being blocked by any upstream services GitHub uses for Pages hosting/CDN?
2. If the block is external (Google/Microsoft/etc.), can GitHub assist with contacting the right reviewer or provide guidance on the fastest route to request a review?
3. Any recommended troubleshooting steps or telemetry I can provide (logs, HTTP response headers, or screenshots) to help triage?

Attachments:

• Screenshot of browser warning
• (Optional) Netflix.zip — site files for testing

This is urgent — the site is for my portfolio/submission. Any guidance or help to request/expedite a Safe Browsing review would be highly appreciated. Thank you.

[shahkochaki]

Short answer: This is almost certainly a reputation / Safe Browsing classification issue (third-party blocklist) rather than a content issue in your repo. The browser warning is coming from Safe Browsing/SmartScreen/etc., not from GitHub Pages code, so the fix will require a review request to those services — and optionally coordination with GitHub Support.

What’s happening (technical background)

• GitHub Pages sites are served on GitHub’s CDN under *.github.io. Browsers consult third-party reputation services (Google Safe Browsing, Microsoft SmartScreen and others) when deciding to show “Deceptive site ahead”.
• If a specific subdomain (e.g. saniyamujawar04.github.io) was previously flagged for abuse, that reputation can persist even after you replace site content. The block may be applied to the account subdomain or to cached records in the reputation databases.

Concrete next steps (what you should do now)

1. Check Google Safe Browsing directly

   • Visit: https://transparencyreport.google.com/safe-browsing/search
   • Paste your exact Pages URL (e.g. https://saniyamujawar04.github.io/Netflix-clone/) and check the result. If flagged, use the “Request Review” button and keep the review ID or screenshot.

2. Check Microsoft SmartScreen / Bing

   • Use Microsoft’s URL testing / Bing webmaster tools if available to see whether SmartScreen flags the URL.

3. Open a GitHub Support ticket

   • Choose the Pages / Security category and include:
     • Example repo and Pages URL
     • Proof that repo content is safe (link to repo, screenshots)
     • Evidence that same files work when hosted from another account
     • Screenshot of the browser warning and the Safe Browsing check result (if any)
   • Ask GitHub to confirm whether any upstream reputation data or internal block is present for your username.github.io subdomain and request assistance coordinating a delist or guidance to request review

[sepidehghaderi7]

Thank you!

[mecodeatlas]

Hey @sepidehghaderi7, thanks for reaching out!

If your GitHub Pages site is being flagged as dangerous or deceptive, it usually means that a browser or third-party safety provider (like Google Safe Browsing) has temporarily marked your domain.

This can happen for a few different reasons - such as outdated scripts, mixed-content issues, or misconfigured redirects.

We’ve published a short guide that walks you through the most common causes and how to fix them:
👉 GitHub Pages: Site Flagged? Here’s What to Know

It includes troubleshooting steps, verification guidance, and links to request a review once everything’s fixed.

Best of luck!

[lucashawthorne]

I posted this comment in a separate post and was looking to see if I could get any help here:

Yesterday, all of my websites were flagged as Dangerous and I was able to get them unflagged this morning. However, just prior to them being flagged, and even now after they're unflagged, I'm encountering this error on every single one of my websites:

You can see this for yourself if you head to my portfolio, for example. There's nothing wrong with my code or deployment as I've personally seen as well as other people.

I don't know if my websites being flagged as dangerous broke them or something, because I've been having this issue even slightly before the Dangerous flag came up, but for weeks my websites were working fine. Can anyone help me find a fix?