I use it, it works, even recommended it in my Very Light Weight Low Drag Applications under 32-Bit applications... It may, occasionally be slower than using Cloudflare, Quad9 or DNS.SB, but just as often the opposite is true, and SecretDNS is at least on the face of things more private. I say 'on the face of things' because it's not FOSS, so there's no third party audit -- but people that have tested it with WireShark say it's doing the job with no anomalous behavior, and the Developer Kilho Seocho-gu from South Korea is very reputable... The audit issue stands with privacy DNS DNS providers like Quad9, DNS.SB, Cloudflare and more so, as harder to test, they can change anything at anytime and you don't have a hard working individual whose reputation is at stake... So, I'd trust Kilho Seocho-gu more than mega DNS companies -- though you can use both!
I do not wish to continue this discussion but I'm compelled to respond as normal users, reading this thread might get wrong opinion about DNSCrypt, from a factually wrong description 1. DNSCrypt offers blocklists, they can be local or remote. A full-featured client not offering blocklists/whitelists in 2026 is not really a client, let alone full-featured. 2. DNSCrypt offers custom encrypted DNS resolution. Upstream servers with the ability to block Ads/Malware can be used. That's the whole point. 3. Whitelist offers, selective whitelisting of any domain irrespective of what upstream server is doing giving user full control 4. Blocklist/Whitelist can be selectively configured in any way the user likes, could as simple as one line or could be as advanced as specific routing of domains through reley's, use of the regex and advanced formats. But everything remains optional, DNSCrypt could serve a normal user with minimal configuration and has advanced features for power users should they desire. This flexibilty is exactly what makes DNSCrypt such an appealing project. 4. DNSCrypt literally takes less than 10 MB, runs quietly in the background without disturbing the user, latency within DNSCrypt Windows pipes is less than 2ms, I don't understand how can this be any "overhead" or "performance loss" or "latency". The closest upstream server for TCP/IP with or without DNSCrypt will take ~40/50 if the user happens to be very close to the upstream server. I don't see overhaed, performance or latency from going 40 to 42ms. Also, 90% of the users can't achieve anything below ~50. DNSCrypt is just an advanced DNS client replacing the Windows DNS with far more advanced features at the cost of 10MB. 5. Any user who can't learn and built their own config file (only needed once in a lifetime) should not try any advanced ways to use their PC anyways. They should stick to what Microsoft provides and Microsoft preferred configurations.