I'm currently using ControlD with New Domain in 30 days blocking enabled. Is there a way for me to confirm whether their filtering is working?Last time I tried ControlD, it failed NRDs! How the hell do you fail that? It is dumb proof, if the domain is less then 30 days old, you block it, but they cheated!
DNS Providers for Home Users – Still Cloudflare/Quad9, or Did NextDNS/Control D Finally Win?
- Thread starter Bot
- Start date
- Featured
ControlD uses a feed of domains registered daily.
They will not perform a real time whois on all domains, as this will be costly, unreliable and very slow.
The feeds come from a third-party supplier.
If the supplier has issues such as delays, technical problems, poor coverage and so on, ControlD inevitably fails at blocking NRD.
Cloudflare has much better partnerships than ControlD.
However, the standard 1.1.1.1 with malware blocking is the mediocrity itself.
They will not perform a real time whois on all domains, as this will be costly, unreliable and very slow.
The feeds come from a third-party supplier.
If the supplier has issues such as delays, technical problems, poor coverage and so on, ControlD inevitably fails at blocking NRD.
Cloudflare has much better partnerships than ControlD.
However, the standard 1.1.1.1 with malware blocking is the mediocrity itself.
ControlD works for me. I have a 20 USD yearly subcription.
Opps editied to $20 USD for full control. My Windscribe plan is 10 USD yearly.
Opps editied to $20 USD for full control. My Windscribe plan is 10 USD yearly.
Last edited:
ThanksYou can use:
DNS leak test
www.dnsleaktest.com
This is very informative, thanks. I set up a free account to try Cloudflare Zero Trust, and it seems to offer more content and security filtering options than ControlD. However, ControlD has AI-based malware filtering and supports third-party blocklists from Hagezi. CFZT portal also includes network filtering and HTTP filtering settings but I'm not sure of their effectiveness.
This test shows which DNS you're using, not if the DNS filtering is working.You can use:
DNS leak test
If someone wants to test if their DNS filtering is working correctly, they can either visit a domain present in the blocklist one uses, or manually block some domain in the control panel and then try to visit it. If you can't access the website under blocked domain, then the filtering works. If you can still visit the website, then something went wrong.
Last edited:
It shows that the request is sent properly to the DNS resolver. This method is recommended by Control D.
This method cannot show what Control D is doing with the request. The method posted by you also cannot be used to confirm if all aspects of filtering work well. This would require more comprehensive testing on URLs.
Actually, what these DNS leak testing sites do is fire up bunch of requests in order to find out which DNS resolvers resolved the query. The purpose of these sites is to show you if any requests were answered by DNS resolver that you didn't set or use.
Correct method would be test all blocked domains, but it's hella lot of work and testing few random domains will do the job. Beside, you can always look at logs to see what was blocked and what not.
