No More DPI 1.1.0

No More DPI

Gets sites that your network blocks or slows down with deep packet inspection working again, for every app on the PC. You list the domains; only those go through byedpi. No VPN, no proxy setting in each app.

No sites are included: after installing, open Profiles and add the domains you need.

Download 1.1.0
FileNoMoreDPI-1.1.0-setup.exe
Size70.3 MB
Released4 November 2026
SystemWindows 10 1809+ or 11, x64
LicenseFree, MIT

Release notes · All releases · Source code

The installer is not code-signed. If SmartScreen says it “protected your PC”, choose More info, then Run anyway.

The Status page: active, two profiles running, DNS statistics
No More DPI: Active 16:26 03.11.2026
The Status page and the tray icon. A Windows service does the work; the window and the icon only control it.

What it does

Per domain, not per app
Your browser and desktop apps all follow the same rule. Subdomains are included.
Leaves the rest alone
Only listed domains go through the bypass. Other traffic goes out directly, unchanged.
Encrypted DNS
Names are resolved over DNSCrypt or DNS-over-HTTPS, so the network cannot tamper with the answers.
Auto-find
Tries known byedpi settings on your current connection and keeps the first one that works twice in a row. Run it again on a new network.
Fails open
If the service crashes or is stopped, DNS goes back to what it was. Your internet does not go down with it.
Nothing phones home
No telemetry, no accounts, no update checks.

How it works

DNS TCP Any app browser or desktop app No More DPI resolver 127.0.0.1:53 Encrypted DNS DNSCrypt or DoH real IP profile domain → 100.79.x.x · other → real IP Wintun adapter 100.79.0.0/16 only byedpi one process per profile Blocked site at its real IP reshapes the TLS handshake Other sites everything else: straight out, unchanged Any app browser or desktop app DNS TCP Resolver 127.0.0.1:53 Encrypted DNS DNSCrypt or DoH profile domain → 100.79.x.x anything else → the real answer Wintun adapter 100.79.0.0/16 byedpi one per profile Blocked site at its real IP Everything else Other names and connections go out directly, unchanged.
  1. The service points each network adapter’s DNS at its own resolver on 127.0.0.1 and ::1, which asks Quad9, AdGuard or Cloudflare (by default) over DNSCrypt or DoH.
  2. A name in a profile gets a fake address from 100.79.0.0/16. Only that block is routed into the Wintun adapter.
  3. Connections arriving there go to that profile’s byedpi, which connects to the real address and reshapes the start of the TLS handshake so DPI no longer recognises it.
  4. For profile domains, QUIC is dropped so browsers use TLS over TCP, and IPv6 answers are withheld.

Details: ARCHITECTURE.md.

Screenshots

The Status page: active, two profiles running, DNS statistics
StatusWhat is running, traffic per profile, pause and resume.
The Profiles page with two example profiles a user added
ProfilesDomains and byedpi arguments per profile, Auto-find.
The Advanced page: DNS lock, DNS servers, fake IP range
AdvancedDNS servers, DNS lock, fake IP range. Needs admin.
The Settings page: service control and app options
SettingsStart, stop, startup type, theme, logs, uninstall.

Tray icon

RingMeaning
GreenActive
GreyPaused, everything goes out directly
RedError, open the window for details
YellowThe service is not running

Requirements

Windows10 version 1809 or later, or 11
Processorx64 only, no ARM64 build
RightsAdministrator, to install and to change machine-wide DNS settings
RuntimeNothing to install, .NET is included

Latest release

1.1.04 November 2026On GitHub
  • No profiles are included any more: a new install starts with an empty list and you add a profile for each site you need. Existing installs keep the profiles they have.
NoMoreDPI-1.1.0-setup.exe70.3 MB
NoMoreDPI-1.1.0-setup.exe.sha25693 bytes

SHA-256 27ae35b77fd0df29631ff43ce633d303be2b6ce1b97b0560912f775ffef92f0e

Help

A site in a profile still doesn’t open.
Open Profiles and click Auto-find on that profile. Check that the site’s other domains (CDNs, APIs) are listed too; the service log names failed connections. Then restart the app or browser.
Browsers say “Managed by your organization”.
That is the DNS lock. It turns off the browsers’ own secure DNS by policy so they keep using No More DPI. It is put back when you pause, turn the lock off or uninstall.
The status says Error.
The Status page gives the reason. Often another program already uses port 53. Stop it, then click Resume.
No internet after a crash.
The service restores DNS when it starts again. If it can’t, run "C:\Program Files\No More DPI\nomoredpi-svc.exe" restore, or uninstall.
Is it a VPN?
No. Your network still sees which IP addresses you connect to. It doesn’t help against blocking by IP, and only TCP goes through byedpi; voice and game servers that apps reach without a DNS lookup are not routed, and are usually not blocked.
How do I remove it?
Settings → Uninstall No More DPI, or Settings → Apps in Windows. It removes the service, adapter, filters and policies and restores your DNS.