Compare
More than DNS filtering.
DNS filtering blocks a site by its name. That stops a lot, and it's a good start. Here is what it can't see, and how Walltunnel's two further checks close the gap.
What DNS filtering does
Before a device connects to a site it looks up the site's address. A DNS filter answers that lookup, and refuses known bad names. It is cheap and fast, and it covers phones when set up as a profile.
What it misses
- Bad pages on good sites. A phishing page hosted on a well-known file-sharing service has a trusted name. DNS filtering lets it through; Walltunnel inspects the page itself.
- Infected downloads. A malware file from a legitimate site passes a name check. Walltunnel scans the file before it reaches the disk.
- Apps that bring their own DNS. Browsers and malware can use encrypted DNS of their own and skip the filter. Walltunnel refuses those connections at the network.
- The Wi‑Fi itself. DNS filtering doesn't encrypt anything else; on hotel Wi‑Fi everything else is exposed. Walltunnel's tunnel encrypts all of it.
| DNS filtering | Walltunnel | |
|---|---|---|
| Blocks known bad sites by name | Yes | Yes |
| Checks the exact page | No | Yes |
| Scans downloads | No | Yes |
| Can't be skipped by an app's own DNS | Easily skipped | Yes |
| Encrypts all traffic | Lookups only | Yes, post-quantum |
Last updated 14 October 2026.