Enforces strict DNS-over-HTTPS, blocks WebRTC IP leaks, disables telemetry, and strips tracking headers — all before Discord touches the network.
Discord runs on Chromium. That means plaintext DNS, WebRTC IP leaks, and fingerprinting headers — unless you patch it at the source.
All DNS queries forced through Mullvad's encrypted DoH resolver. Plain DNS fallback removed — queries fail securely rather than silently downgrade.
Blocks non-proxied UDP via disable_non_proxied_udp. Your local LAN IP is never exposed to Discord's voice servers or other call participants.
Cancels requests to /science, /track, /analytics, Sentry, Mixpanel, Segment, and Amplitude at the Electron network layer.
Strips Electron/x.x.x and DiscordApp/x.x.x from all outgoing headers so servers cannot fingerprint your exact Electron build.
Minimum TLS enforced via setSSLConfig. Connections to servers using outdated, insecure TLS are blocked entirely.
All geolocation requests denied at the Electron layer via both setPermissionRequestHandler and setPermissionCheckHandler.
Chromium's spellchecker — which can send typed text to remote cloud APIs — disabled via setSpellCheckerEnabled(false).
Google's Chromium ID header plus X-Goog-Visitor-Id and X-Firebase-Client stripped from every request via webRequest.onBeforeSendHeaders.
Breakpad crash reporting disabled and upload endpoints blocked independently. Your crash data stays on your machine, not Discord's servers.
DcDNS prepends a JS payload into Discord's index.js. Every protection fires before Chromium opens a single socket.
.exe, zero install. Admin privileges are required to write into Discord's installation directory — nothing else is modified on your system.index.js is backed up as index.js.dcdns.bak before anything is written.index.js. It hooks Chromium's session API — DoH, WebRTC policy, header filters, and permission handlers all activate here."Encrypted by DcDNS" when the patch is active. All protections are live before the first DNS query leaves the machine.index.js, removing the patch. Just re-run DcDNS and click Install — your settings are saved in dcdns_conf.json and reapplied automatically.index.js with a clean copy. Re-run DcDNS and click Install to restore the patch — your configuration is preserved.
DcDNS improves network-level privacy within Discord. Every claim here is checkable — source code, no obfuscation, no telemetry, no install.
Every line — Python launcher, JS payload injected into Discord, and this page — is public on GitHub. Read it before you run it. There are no compiled black boxes and no minified blobs that hide behavior.
The patcher transmits nothing. The only external request is a read-only GitHub API call to check for a newer version — it sends no identifiers and reads only public release metadata. You can disable it by blocking api.github.com.
Before writing anything, DcDNS saves the original index.js as index.js.dcdns.bak. Click Uninstall and it's restored exactly. If the backup is missing, the injected payload is cleanly stripped by marker — the file is never left in a broken state.
The SHA-256 of the .exe is computed from the binary at runtime and shown in the UI — and published in each GitHub release. Verify it yourself with certutil -hashfile DcDNS.exe SHA256 before patching anything.
Patching Discord's client files is not something Discord officially allows. Their Terms of Service prohibit modifying the client, and using DcDNS puts you in that category. Discord could detect the modification and ban your account — in practice this hasn't been reported, but that doesn't mean it's impossible.
This tool exists for people who've already decided they want more control over what Discord sends over the network. If you're not comfortable with the risk, don't use it. The source code is public so you can read exactly what gets injected before you touch anything.
You're doing this on your own terms. The author takes no responsibility for bans, broken installs, or anything else that happens as a result of using DcDNS. Back up your Discord installation before running it if you're unsure.
Full release history — latest always at the top. Fetched live from GitHub.