Domain not blocked when expected to be blocked


Expected Behaviour:

I added to the Settings > Block Lists and expect that sites like will be blocked

Actual Behaviour: is still accessible

If I add to the Blocklist (wildcard) then I can confirm that is blocked. But I expect that it will be blocked using the gravity list.

Debug Token:



It seems to be blocking now. Is there gap between the list updated and it actually starts to block? Thanks.


The block list you referenced blocks “”, but not “”. These are two different domains and it is likely that the domain you were able to access was “” Here is a quick way to check your pihole.log and see if this is the case - this command will find every instance of “pornhub” in your log.

sudo grep pornhub /var/log/pihole.log

If “” was shown as blocked, and “” was not, this was the problem.


In that case, what do I do so that for all domain listed in the www equivalent of the domain names are block as well?

It is strange that when I randomly test the sites listed there, not all of them blocked while pornhub is remain blocked.


Pornhub is likely blocked because you have blacklisted it as a wildcard.

If the public block list you are using does not adequately block the “www” equivalents, then feedback to the list maintainer would be in order.


Actually I don’t think the issue is about with/out WWW. Trying out sites listed on the above list, some of them that are blocked on Chrome I still can access through Firefox. How is that even possible?


Firefox has an option to run it’s own filtering on it’s own DNS. When you do this, your DNS traffic bypasses Pi-Hole. Check your Firefox options and disable this feature.


Hi @jfb would you please tell me which part of configuration is that? I search for DNS in Firefox settings and found only Proxy DNS when using SOCKS v5 and Enable DNS over HTTPS which both are unticked.

closed #9

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.