Services
Private Services
Observations on private DNS providers and how their responses compare against public ISP resolvers in neutrality tests.
Why private resolvers matter
Private DNS services sit alongside the resolvers operated by Internet Service Providers. Tracking both groups helps separate operator-level filtering from broader patterns visible across the public DNS layer.
- Independent vantage points outside ISP-controlled infrastructure.
- Useful baseline for confirming whether a block originates at the ISP resolver.
- Coverage that complements country-level DNS lists.
Comparison approach
Each private service is probed using the same set of domains examined for public ISP servers. Differences in responses are recorded and grouped by category.
| Aspect | Private DNS providers | Public ISP resolvers |
|---|---|---|
| Operation | Run by third-party operatorsnot tied to the user's access provider | Run by the access providerdefault for many subscribers |
| Use in tests | Reference point for non-ISP behaviour | Primary source of ISP neutrality data |
| Reporting | Listed under Private services | Listed in the DNS Server List |
Private DNS resolvers have become a common alternative for users who want to query the domain system without relying on the infrastructure operated by their Internet Service Provider. Monitoring how these services respond during neutrality tests adds an important layer of context to the broader picture of internet filtering, because it helps separate decisions made by ISPs from patterns that appear elsewhere in the resolving chain. When a private resolver returns a different answer than an ISP resolver, the gap can be a useful signal for researchers who are trying to understand where blocking actually begins.
Independent vantage points are central to the philosophy of a neutrality monitor. By looking at responses from servers that sit outside ISP-controlled networks, the platform can offer a comparison that is not shaped by the filtering policies of a single operator. This kind of cross-check is valuable in countries where regulatory environments vary, and where the behaviour of one resolver cannot be assumed to represent the wider internet. Private resolvers, in this sense, act as reference points that help validate what the public DNS layer is reporting.
A useful baseline emerges when private resolvers and ISP resolvers are tested against the same lists of addresses over the same period. If the private side consistently reaches a host while the ISP side redirects or fails, that contrast points strongly toward operator-level filtering. If both sides agree, the result is more likely to reflect a broader pattern, such as a shared blocklist or a routing issue that affects multiple networks at once. This dual approach makes the data more reliable and more indicative of real conditions.
Country-level DNS lists describe what is blocked within national borders, but they tell only part of the story. Private resolvers, often hosted in other regions, extend coverage beyond that boundary and can reveal whether certain addresses are also restricted or unreachable from outside the country. Combined with daily probes and live statistics, the inclusion of private services produces a fuller picture of how blocking is implemented and how it changes over time, including cases where a site appears active locally but appears missing when checked from abroad.
Transparency around private resolvers also supports the voluntary and community-driven nature of the project. Anyone running an independent server can contribute data, and the platform can then integrate those responses into its published reports. This openness helps ensure that the resulting analysis is not dominated by any single provider and that members and trusted observers can audit the methodology. Over time, a balanced mix of public and private vantage points strengthens confidence in the daily findings that the monitor shares.
Where to look next
Private service data is most useful when read alongside the full DNS list and the country-level reports.