This time, we'll answer a somewhat difficult, technical question.
This includes technical details, but it's totally OK if you don't understand them.
Don't worry if you don't understand all these technical details. Anti Spy Phone is already configured, so anyone can use it easily.
The takeaway (up front)
Encrypted DNS with filtering definitely strengthens your privacy against those "right nearby."
"Right nearby" here means observers along the route, such as your ISP, the operator of a café or workplace Wi-Fi, or someone else on the same network.
They can no longer see "which sites you looked up," something that was previously completely visible to them.
At the same time, however, encrypted DNS does not make you anonymous.
In fact, depending on your settings and the service you choose, it can also make you "stand out as a minority" on the network.
In other words, the honest answer to the question in the title is:
" Both can happen. It depends on whom you want protection from (your threat model)."
In this article, we'll break down at the technical level why both can happen at the same time.
Why is DNS a privacy issue in the first place?
DNS is like a "phone book" that translates names like example.com into IP addresses that computers use to communicate.
Almost every time you open a site or an app communicates, this lookup (query) takes place.
The problem is that traditional DNS is not encrypted.
When DNS was designed, privacy wasn't a consideration, and queries were sent in plaintext. As a result,
- Your ISP can log and analyze which domains you've looked up
- Third parties on the same Wi-Fi can also snoop on or alter your traffic
- In some countries, DNS is used as a censorship "checkpoint"
This is what happens by default.
Encrypted DNS is what blocks this. There are three main protocols.
- DoH (DNS over HTTPS): Uses port 443, just like regular web traffic, so it's harder to distinguish from other HTTPS traffic and less likely to be blocked.
- DoT (DNS over TLS): Uses a dedicated port, number 853. It's straightforward to manage, but because it uses a dedicated port, it's easy to tell that "DNS is encrypted," and it may be blocked on restrictive networks.
- DoQ (DNS over QUIC): A newer method that runs over QUIC
Android's "Private DNS" setting uses DoT (the method configured by hostname).
Anti Spy Phone works basically the same way: you use standard Private DNS or encrypted DNS through an app, as described below.
What encrypted DNS "protects" and "doesn't protect"
This is the point most often misunderstood. Encrypted DNS is not an all-purpose cloak.
What it protects:
- Hide query contents from observers along the route (ISPs, Wi-Fi operators, and intermediaries)
- Prevent tampering with or hijacking communications in transit
What it doesn't protect:
-
The resolver operator can see everything Encrypted queries are ultimately decrypted and processed by some DNS resolver. In other words, you could say you've only shifted where you place your trust - from "what you showed your ISP" to "what you show your DNS provider." If the provider keeps logs, your activity history accumulates there.
-
Which resolver you're connecting to is not hidden With both DoH and DoT, the IP address of the server you're connecting to and the server name used during the TLS connection (SNI) are visible along the route (unless ECH, which encrypts SNI, is enabled). Even if the contents can't be read, observers can still see that "this person is connecting to ◯◯'s DNS."
-
Even the sites you visit can be inferred despite encryption Academic research has shown that even with encrypted DNS traffic, the "shape" of the traffic - such as packet sizes, counts, and timing - can reveal which websites you visit with fairly high accuracy (including the NDSS 2020 paper by Siby et al. and research by Bushart et al.). EDNS0 padding is a mitigation, but reports say its effectiveness is limited.
The second and third items in this list of things it "doesn't protect" are what lead to the "standing out" mentioned in the title.
4 mechanisms that make you "stand out"
Centralized trust in the resolver
Visibility that was distributed across ISPs is concentrated in a single DNS provider.
If the provider doesn't keep logs, has been audited, and operates in a favorable jurisdiction, these can be advantages. Conversely, the very structure of “entrusting everything to one place” can also focus the target for attacks or disclosure requests in one place.
② The “fixed identifier” that is a profile ID
Customizable services like NextDNS and modDNS create a configuration profile for each user and embed its unique ID in the DoH URL path.
For example, with NextDNS, it's the abc123 part of https://dns.nextdns.io/abc123/....
This ID is hidden inside TLS along the network path, but from the resolver operator's perspective, all your queries are linked to the same ID.
NextDNS also has a feature that adds device names and device IDs (X-Device-Id) to logs. While useful, this reinforces their role as identifiers.
A profile ID is a value that can remain unchanged for a long time, making it a potential “fingerprint.”
③ The connection destination as a fingerprint = size of the anonymity set
This is the key factor determining whether you stand out or go unnoticed.
As mentioned above, the resolver you're connected to is visible along the network path.
That means the more people on that network using the same resolver, the more you blend into the crowd (a larger anonymity set).
Conversely, if you connect to an unusual resolver that almost nobody uses, you stand out as part of a small minority (a small anonymity set): “This is the only person on this network using that DNS.”
The irony is that privacy-focused setups, such as an “anti-spyphone device + a new DNS service with few users,” are unusual in themselves, making them easier for observers to identify.
④ Traffic analysis
Even if you conceal all of ①–③, as discussed in ③, there's still a risk that the sites you visit can be inferred from the “shape” of encrypted traffic.
This is a challenge common to encrypted communications in general, not just DNS, and it's not easy to fully address.
Comparing the four services from this perspective
First, it's important to understand that these four are not comparable on the same basis.
- modDNS / NextDNS / AdGuard DNS … “Resolvers (services)” that resolve and filter queries.
- RethinkDNS … A “client (+ firewall)” that doesn't have its own resolver and lets you choose any upstream resolver.
With this distinction in mind, let's look at each from the perspectives of both “enhanced privacy” and “visibility.”
modDNS (IVPN)
A new filtering DNS developed and operated by VPN provider IVPN. It was released in March 2026 as a beta for IVPN Pro users.
- Strengths: Open source (GPL-3.0) and audited by Cure53 in 2025. Supports DoH/DoT/DoQ. Query logging is disabled by default. After registration, identifiers related to modDNS are separated from IVPN's core systems, a design intended to prevent them from being linked to an account.
-
Visibility: Each profile has a unique identifier (mechanism ②). In addition, it is still in beta with few users, and its servers are concentrated in North America and Europe. For now, bear in mind that a small anonymity set makes the service more conspicuous as a connection destination.
NextDNS
A popular public DNS service for its customizability (based in the US).
- Strengths: You can finely configure blocklists, categories, allow/deny lists, and more, and adjust (or disable) log retention periods and storage regions.
-
Visibility: The profile ID appears in the DoH URL in the typical case (mechanism ②). On the other hand, a public endpoint that doesn't use a profile (
dns.nextdns.io) is also available, and is included among the options in Firefox and Chromium. Understanding that “using a custom profile = an identifier is present” and “using a public endpoint = blending into the crowd is easier” have different privacy characteristics can help you choose.
AdGuard DNS
A public resolver known for ad and tracker blocking. It also became the world's first public DoQ resolver in 2020.
- Strength: It has a large user base, so as long as you use a public endpoint, the anonymity set is large and it's easy to blend into the crowd (an advantage from the perspective of mechanism ③).
-
Note: It says it retains server performance metrics (such as request counts, block counts, and processing speeds) and a database of requested domains from the past 24 hours to identify new trackers. Keep in mind that it does not have a completely log-free policy.
RethinkDNS
An open-source client for Android. Think of it as a tool for managing how you use resolvers, rather than how you choose them.
- What it can do: Supports DoH/DoT/DNSCrypt/DNS proxies, caches DNS responses, keeps local query logs on your device, and works as a per-app firewall.
- Android limitations: Because it uses Android's VPN slot, it is generally mutually exclusive with other VPNs (though you can use it alongside a VPN or Tor by importing a WireGuard configuration or using Orbot as a proxy, for example).
-
Privacy considerations: RethinkDNS itself leaves the choice of resolver up to you. In other words, the size of your anonymity set and whether you have an identifier depend on the upstream resolver you choose through Rethink. It is a powerful tool, but the key question is not “Is it safe because I installed Rethink?” but “What am I connecting to through Rethink?”
So, how should you choose? (By threat model)
There is no single “right answer.” It depends on who you want protection from.
Case A: You don't want your ISP or Wi-Fi operator to see your activity (the most common case) Encrypted DNS is clearly effective.
Choose a popular, established resolver (a public endpoint) to benefit from a large anonymity set and blend in more easily. You also get ad and tracker blocking.
For many people, this is enough.
Case B: You don't want the DNS provider to consolidate your activity either
Choose a service that explicitly states it keeps no logs, is audited if possible, and has a favorable jurisdiction.
If you use a custom setup with a profile ID, understand that you are “trading convenience for a fixed identifier.”
For additional protection, options include systems such as ODoH (Oblivious DoH), which separates “who (IP)” from “what (query),” and methods such as Anonymized DNSCrypt, which hide your IP through a relay.
Case C: Blending in on the network is itself important This is the most difficult case.
Unusual resolvers or special configurations can make you stand out instead.
For this purpose, it makes more sense to tunnel all traffic through a VPN or Tor, consolidating even the DNS destination fingerprint at the exit, rather than tweaking DNS alone.
DNS over Tor is powerful, but comes at the cost of speed.
If you use an anti-spy phone, you can take a gradual approach: easily encrypt your DNS with standard Private DNS (DoT), use RethinkDNS for per-app controls, or combine it with a VPN.
At every stage, it may seem like a detour, but the surest approach is to first put into words “Who am I trying to hide what from right now?” and then choose your settings.
Summary
- Encrypted and filtering DNS clearly strengthens privacy against observers along the network path (ISPs, Wi-Fi operators, and intermediaries). Blocking ads and trackers also offers substantial practical benefits.
- On the other hand, it does not provide anonymity. Visibility is concentrated with the DNS provider, a fixed identifier called a profile ID is created, and there is still a chance of being identified from the destinations you connect to and the “shape” of your traffic.
- Unusual services or niche configurations can make you “stand out” as part of a minority. The size of the anonymity set is an important aspect of privacy that is easy to overlook.
- So “Does DNS filtering improve privacy or make you stand out?” isn't an either-or question; both can be true at the same time. What matters most is not which features are better, but your own threat model.
DNS settings aren't a magic switch that makes you safe just by turning them on.
Decide what you want to protect against, then choose your tools - as long as you keep that order, encrypted DNS is a very reliable ally.
0 comments