DNS4EU one year on: Europe's sovereign resolver looks for a business model
Published July 2, 2026 · DNS Benchmark Pro Editorial · Reading time: 3 minutes
In short — Launched in June 2025 to reduce Europe's dependence on American resolvers, DNS4EU has passed its first birthday. Adoption is voluntary, and the EU funding that built it was never meant to run forever.
DNS4EU went live on 9 June 2025 with an explicitly political brief: give Europe a public DNS resolver that is not operated by Google, Cloudflare or Cisco. Built by a consortium led by the Czech security firm Whalebone with EU funding, it resolves queries inside the EU, blocks known malicious domains, adheres to GDPR by design, and supports both DNS over HTTPS and DNS over TLS.
A year on, it is worth being honest about where it stands.
What it does well
The privacy story is the strongest part. DNS4EU's operating premise — queries resolved within EU jurisdiction, under GDPR, by an operator with no advertising business — is a materially different proposition from the American incumbents, and one that no amount of privacy-policy language from a US provider can fully replicate. For European public-sector bodies with data-residency obligations, that is not a marketing claim; it is a compliance requirement they can now satisfy without running their own infrastructure.
It also ships filtering profiles: plain resolution, malware blocking, ad blocking, child-protection filtering, and combinations thereof, each on its own set of addresses. That is a sensible design, and more configurable out of the box than 1.1.1.1 or 8.8.8.8.
What it is up against
Two things, mainly.
The first is physics. Cloudflare's latency advantage comes from an anycast footprint of hundreds of points of presence built over a decade; Google's comes from being everywhere that Google is. A resolver deliberately confined to EU infrastructure is competing on a smaller network. Within Europe the gap narrows considerably — and for many European users DNS4EU is genuinely competitive — but it is not going to win a global benchmark, and it was never designed to.
The second is inertia. Adoption is entirely voluntary. No ISP is compelled to adopt it, and home users have to point a router or a device at it by hand. The expectation has been that government ministries and telecom operators move first, with specialised deployments folded into existing security stacks, and consumer adoption follows slowly if at all. That is a realistic plan, but it is a slow one.
The funding question
DNS4EU was built with EU money on a defined grant, with the stated intention of introducing commercial offerings — premium SLAs for governments and operators — to sustain the service beyond the funded phase. How that lands is the thing to watch. A publicly funded resolver that becomes a commercial product is a different animal from one that stays a public good, and the free public endpoints' long-term status is the detail European users should keep an eye on.
Should you use it?
If you are in Europe and jurisdiction matters to you — because of regulation, or because you simply prefer your query log to sit under GDPR — it belongs on your shortlist, and you should benchmark it from your own connection rather than trusting anyone's published numbers, including ours. Resolver latency is intensely local. The right answer in Lisbon is not the right answer in Helsinki.
If you are outside Europe, there is little reason to route your DNS through the EU.
Sources: joindns4.eu, "DNS4EU Public Service Goes Live"; DNS4EU project overview; DENIC Blog, "DNS4EU — Kick-Off for Developing a European Resolver Infrastructure".
Published by Genext Information Systems · July 2, 2026. DNS Benchmark Pro is an independent tool and is not affiliated with any vendor or organisation named in this article. This report summarises publicly available disclosures and is provided for informational purposes.