DNS for Families Not Blocking Site After Tag Update
Hey everyone,
I recently started using DNS for Families and it was working great at first. However, I encountered an issue with a site: chatmate.tv, which is an adult chatting website.
Initially, it was only tagged as "technology" on Cloudflare Radar, so I reported it to Radar for proper categorization. After waiting a full 24 hours (thinking that’s how long it might take for the DNS to update), I checked again and saw it’s now correctly tagged as "adult" and "CIPA".
However, even after the reclassification, the site is still accessible through the DNS resolver.
Does anyone know why this might be happening? Should I wait longer or is there something else I need to do on my end?
Thanks in advance! 🙏
9 Replies
I don't believe 1.1.1.1.3 / DNS for Families Blocks Adult Themes
there used to be docs on this somewhere but I can't remember, it's easy to test with Cloudflare's testcategory domain though
chaik@ash:~$ dig adult-themes.testcategory.com @1.1.1.3 +short 104.18.5.35 104.18.4.35 chaik@ash:~$ dig nudity.testcategory.com @1.1.1.3 +short 0.0.0.0 chaik@ash:~$ dig pornography.testcategory.com @1.1.1.3 +short 0.0.0.0ehh testcategory looks like it's a wildcard actually, might just be not recognizing adult-themes. Could just be simple propagation time, would probably wait a week or so and see All of the other similar sites are directly tagged Pornography, even 4chan is lol, just going to suggest that tag alongside adult themes
Yeah, that's what I was thinking. Since it's now tagged with "CIPA Filter," I assumed it should be blocked by DNS for Families, given that CIPA usually means filtering adult content.
I flushed my DNS and tested across multiple devices and networks, just in case, but it's still accessible. From what I’ve seen, DNS updates usually take less than 24 hours, so this is a bit surprising.
Still, it could just be a delay or something specific to how Cloudflare handles those tags. I’ll wait a few more days and check again.
It's not about DNS Updates but Cloudflare updating the filter list on their end for 1.1.1.3's service
but yea it's def not dns cache or anything, you can query directly and it's not blocked
I think it's more that it's not under Pornography/Nudity, I made the category suggestion
thanks!
no update on this still, do you know an email i might be able to contact?
no email for support; it looks like they rejected or haven't applied the categorization request to Pornography yet
yeah i think they rejected because before it even had the CISP tag it only took 1 hour to update
If you need something more custom and flexible, Zero Trust is free (although requires a payment method for anti abuse reasons), and you can create your own DNS blocking policies based on categories, or even blocking specific domains, and use it via DoT/DoH, plain dns, etc
or you can self host something like Adguard home or Pihole locally, configure your local stuff to use it, and setup adblocking/etc
yeah I think I'm just going to switch services, or self host thanks!
In terms of purely escalation stuff, no employees from radar is in this discord, they're on the Cloudflare community forum, if you have a cloudflare account could post there trying to reach but meh, I don't think not categorizing it as Pornography is wrong, but it not blocking "Adult Themes" for 1.1.1.3 is a curious decision