April 8, 2020 at 8:32 pm
Thanks, these should be blocked in about 24 hours.
ThanksApril 8, 2020 at 6:42 pm
Sorry for the very big delay here, it was caught in pending and didn’t realize it. I have gone ahead and updated the category.
TonyMarch 2, 2020 at 3:47 am
Got it, it’ll be updated in about 24 hours.
ThanksFebruary 27, 2020 at 4:46 pm
Thanks for sharing. I’ll get working on testing these out.
TonyJanuary 2, 2020 at 3:51 am
It should be working now. Apologies for that.
TonyDecember 13, 2019 at 4:03 pm
No, it doesn’t prevent access to other device controls, only the app.
CleanBrowsing SupportOctober 21, 2019 at 4:42 pm
Categorigy does real time updating when a domain is provided. This means that there might be some instances where it shows it has been categorized as Adult, but not reflecting that categorization in the filters. Categorify is checked every 24 hours (+/-) to see what has been added.
If you’re ever curious if what you see in categorify is on the filter you can run this nslookup query:
nslookup redteenpXXX[.]net 126.96.36.199 Server: 188.8.131.52 Address: 184.108.40.206#53 ** server can't find redteenpXXX[.]net: NXDOMAIN
What you’re doing here is asking our Free Adult filter if it recognizes the domain you’re curious about. In this instance I’m checking one of the ones you provided and the response tells me that it is indeed blocked: server can’t find redteenpXXX[.]net: NXDOMAIN.
October 19, 2019 at 6:30 pm
- This reply was modified 2 years, 8 months ago by Daniel Cid. Reason: removing links to adult content
Wow, super thanks for the strong endorsement. The team appreciates it.
TonyOctober 19, 2019 at 6:28 pm
No problem. Thanks.October 17, 2019 at 6:37 am
We updated our guide on iOS to better explain how to use DNSCloak with customer plans. Hope this helps: https://cleanbrowsing.org/guides/iphone
ThanksOctober 17, 2019 at 6:36 am
Would you mind configuring things locally first? It’d help narrow things down.
Also, could you share the output of these commands so we can better understand what is going on locally:
nslookup -type=txt whoami.lua.powerdns.org
nslookup http://www.google.com 220.127.116.11
nslookup -type=txt -class=chaos version.bind 18.104.22.168
nslookup -q=TXT mylocation.whois.dnscontest.cleanbrowsing.org
nslookup -q=TXT mylocation.whois.dnscontest.cleanbrowsing.org 22.214.171.124
ThanksOctober 17, 2019 at 6:31 am
Here are some guides that might help you configure things on your mobile devices: https://cleanbrowsing.org/guides/October 17, 2019 at 6:29 am
Sorry about the delay. Have gone through and recategorized a bunch of them. Please give it about 24 hours to take affect.
ThanksOctober 17, 2019 at 6:09 am
We support the main ones that support it:
YandexOctober 17, 2019 at 6:08 am
The devices would be based on the devices on the network, not just the router. The team is pretty flexible with the utilization, yes the 21st device would get picked up. What might help is if you engage the team directly at firstname.lastname@example.org, they can help answer your questions about the plans and help with getting a trial set up.