DNS failure for deployed github page

[PD-LUHC]

Not sure if this is a bug that can be fixed at repo level or if it is an issue specific to certain departments or a wider issue. The deployed github page for this repo and anything else on https://best-practice-and-impact.github.io/ is being blocked by NCSC DNS protection rules.

Its likely a problem particular to a given department, but I thought repo owners might want to be aware that their material is being blocked from at least some of the intended audience.

[PD-LUHC]

FWIW, someone in our department spotted that cloudflare has marked the domain for phishing:

https://radar.cloudflare.com/domains/domain/best-practice-and-impact.github.io

I guess that a CDN level issue implies that it is a more universal problem.

The domain is still accessible from my private devices, but I guess that makes sense as they don't sit behind a government firewall

[MWilson92]

just want to add to this that everyone in my organisation receives this when trying to access with no way to access the site.

[PD-LUHC]

just want to add to this that everyone in my organisation receives this when trying to access with no way to access the site.

If it's an issue with DNS categorisation then from the very little I know it could well manifest as a certification error. As a hazy guess this could well be dependent on the individual access/firewall policies that a user is subject to.

I guess what I am saying is that the error I originally posted (experienced by everyone I've spoken to in our department) and the error and the error experienced by @MWilson92 and his colleagues, could be local manifestations of the same underlying problem.

It's probably an issue beyond this repo, but it wasn't clear where to raise this so I picked what looked like the most prominent repo under best-practice-and-impact

In any case I don't think this will go away by itself.

[RSHayward]

This is also an issue for DfE computers. If I'm on the work VPN, or even govwifi on my personal phone, I can't access it. I can read it on my phone at home, but that's less than ideal.

[ajtucker]

I had the same problem earlier today and tracked it down to using Cloudflare's malware blocking 1.1.1.2 as my DNS resolver.

As mentioned above, Cloudflare lists this domain as both "CIPA Filter" (children's internet protection act) and "Phishing" in their DNS blacklist, presumably because some keyword or bad/wrong email address is somewhere in one of the GitHub pages sites.

There is a feedback form at https://radar.cloudflare.com/domains/feedback/best-practice-and-impact.github.io, but before asking to be removed from the DNS blocklist it might be worth having a scan through the HTML/markdown to see whether anything jumps out.

[alice-hannah]

For info, we also had this problem in Scottish Government, but it has now been resolved. This is what our IT dept said:

We believed the issue to be with the website owners but on in-depth investigation, discovered it was a website categorisation issue with our DNS provider which manifested incorrectly to Zscaler. We have had the site re-categorised.

[CHCRowley]

I had the same problem earlier today and tracked it down to using Cloudflare's malware blocking 1.1.1.2 as my DNS resolver.

As mentioned above, Cloudflare lists this domain as both "CIPA Filter" (children's internet protection act) and "Phishing" in their DNS blacklist, presumably because some keyword or bad/wrong email address is somewhere in one of the GitHub pages sites.

There is a feedback form at https://radar.cloudflare.com/domains/feedback/best-practice-and-impact.github.io, but before asking to be removed from the DNS blocklist it might be worth having a scan through the HTML/markdown to see whether anything jumps out.

I think it was an issue with Cloudflare miscategorisation, we requested a review and the domain seems to be clear now so can I check you can access it again @PD-LUHC @RSHayward @MWilson92 @ajtucker?

[MWilson92]

Hi @CHCRowley, my team and I can now all access the site again - the review seems to have done the trick for us :)

[ajtucker]

Thanks, @CHCRowley, that works for me!

[CHCRowley]

I'm going to close this issue as it seems to have been fixed - thanks everyone for your help resolving this!