What is Applied Privacy DNS?
Applied Privacy DNS is a free public DNS service run by Applied Privacy Foundation, based in Austria. It offers encrypted DNS only (DoT, DoH); there's no public plain DNS address. It mainly serves Austria: nearby it can be the fastest, but from far away it's usually slower than the big global services.
It checks DNSSEC (domain signatures): answers with a bad signature are refused, so they can't be forged. It doesn't filter anything: every name resolves normally. It's run by a non-profit. Its operator says it doesn't keep your IP address.
Applied Privacy DNS server addresses
To use Applied Privacy DNS, enter:
DoT / Private DNS dot1.applied-privacy.net
DoH https://doh.applied-privacy.net/query
How to set up Applied Privacy DNS
Windows 11
Windows only uses encrypted DNS on top of a plain DNS address, and Applied Privacy DNS doesn't publish one. Use it in your browser (see below) or through a local DNS client such as dnscrypt-proxy.
macOS
On macOS, encrypted DNS comes from a configuration profile: install a DNS profile for https://doh.applied-privacy.net/query.
iPhone and iPad
Install a DNS profile for https://doh.applied-privacy.net/query, then turn it on in Settings → General → VPN & Device Management → DNS.
Android
Settings → Network & internet → Private DNS → Private DNS provider hostname, and enter dot1.applied-privacy.net. It works on every network and is encrypted (DoT). Menus vary a little by brand: search Settings for “Private DNS”.
Router
Routers only take plain DNS addresses, and Applied Privacy DNS doesn't publish one. On OpenWrt, https-dns-proxy can forward to https://doh.applied-privacy.net/query.
Browser
Chrome: Settings → Privacy and security → Security → Use secure DNS → Custom, and enter https://doh.applied-privacy.net/query. Edge has the same option under Privacy, search, and services. Firefox: Settings → Privacy & Security → DNS over HTTPS → Max Protection → Custom, and enter https://doh.applied-privacy.net/query.
Does Applied Privacy DNS work in mainland China?
Its plain DNS usually answers, but more slowly, because the servers are outside mainland China, and answers for blocked sites can be forged on the way. Its encrypted DNS (DoH, DoT) is often blocked or unreliable. The easiest way to know is to run the test on this page: if the result says “Can't be reached from your network”, your network can't reach it.
Applied Privacy DNS or Mullvad DNS: which is faster?
Neither is faster everywhere. It depends on how far each one's nearest server is from you and how your internet provider routes traffic there. This page times Applied Privacy DNS from your own network in a few seconds. To compare it with the others, run the test on the home page: it times every resolver in the list and shows which is fastest for you.
Test all 33 resolvers to see which is fastest →
Mullvad DNS: addresses and setup →
Why is Applied Privacy DNS slow for me?
Usually it's distance: its nearest server is far from you, or your provider takes a long route there. With a proxy or VPN on, the queries go through it too, so the test times the proxy's route (the direct rules fix that). Some networks slow down or block encrypted DNS. And a name nobody has looked up yet always takes longer (the first-lookup time under the result). To see whether another resolver is faster for you, run the test of them all on the home page.
How do I change my DNS?
Android 9 and later: Settings → Network → Private DNS, and enter the DoT hostname (for example one.one.one.one). It works on every network and is encrypted.
iPhone and Mac: enter the DNS servers for each Wi-Fi network. For encrypted DNS, install a configuration profile from the resolver's website.
Windows 11: Settings → Network → your connection → DNS server assignment → Manual. Enter the servers and turn on DNS over HTTPS.
Router: enter the DNS servers in its DHCP or WAN settings, and every device on your network uses them.
Just your browser: Chrome, Edge and Firefox have a Secure DNS setting where you pick a provider or paste a DoH address.
Each resolver's own page has step-by-step setup. Click any address on this page to copy it.
I use a proxy. Is this still my own network's result?
Not by default. With a proxy or VPN on, your browser reaches the resolvers through it, so the test times the proxy's route, and every resolver abroad looks about as fast as your proxy server. The DNS you set on your device or router is normally reached directly, so these numbers aren't what you'd actually get.
To test your own network, add the direct rules (the button next to the progress bar). They send only the addresses this test uses straight out, matched by exact hostname and single IP, and leave all other traffic alone. Clash/Mihomo, Surge, Shadowrocket, Quantumult X, Loon, sing-box and Xray are supported, and most can load the rules from this site so they stay up to date.
How does the test work?
Your browser queries each resolver directly; nothing goes through this site.
First it connects to the resolver and looks up three popular names once, so they're in its cache. That part isn't scored. Then come 10 rounds, each asking it once, so a single hiccup on your network doesn't decide the result. Every other round also looks up a random name that doesn't exist.
The results are medians, so one slow query doesn't drag a score down. Times come from the browser's own network timing, which the page's scripts can't slow down. Every request goes to a new URL and skips every cache, so only the resolver itself can answer.
Why are UDP and DoT estimated?
Because a browser can't measure them. Web pages can only make HTTPS requests: they can't send plain DNS over UDP (port 53), encrypted DNS over TLS (DoT, port 853) or DoQ. No website can measure those from your network; a site that shows such numbers measured from its own server, or guessed.
What this page does instead: it sends DoH, encrypted DNS over HTTPS, to the very server that answers UDP and DoT (for example https://1.1.1.1/dns-query). Once the connection is open, a query takes one round trip to that server plus its processing time. A UDP or DoT query costs exactly that too; HTTPS adds well under a millisecond. Hence the ≈. Where a resolver's plain DNS server doesn't speak HTTPS, you'll see a – rather than a made-up number.
What an estimate can't catch: a network that blocks, slows or tampers with ports 53 or 853 but leaves HTTPS alone.
To measure UDP, DoT and DoQ for real, run the command in the command-line box on this page on a server, a Linux machine or a router. It speaks every protocol and tests this resolver along with the one it's compared with.
How reliable are the results?
The way they're measured is under How does the test work? On top of that, the list is checked from more than one continent with scripts/verify.mjs (in the code repository): every address must answer this kind of query with a real DNS answer, and DNSSEC support is tested, not taken from the resolvers' own claims.
Cloudflare, Google, Quad9, Control D, DNS.SB, DNS4EU and IIJ let web pages read their answers, so the page checks each one and only counts real answers. For the others, the browser can time the answer but not read it.
Run the test a few times, ideally at different hours: what's fastest at night may not be at peak times.
What does First lookup mean?
Popular names are already in every big resolver's cache, so every resolver answers them quickly. A name nobody has looked up in a while is different: the resolver first has to ask that site's own DNS servers, then pass the answer on to you. That's a first lookup.
The test uses random names hosted on Cloudflare, whose DNS servers are almost everywhere except mainland China. This time depends on where each site's DNS servers are, which varies from site to site, so it's shown but not ranked. Resolvers in mainland China get a slow first lookup here because these names' servers are abroad; for Chinese sites they're fast.
What is DNSSEC?
In short: domains sign their DNS records so the answers can't be forged. A resolver that checks DNSSEC verifies the signature and refuses answers that don't match, so nobody along the way can slip you a fake address. A ✓ means the resolver checks it: we test with a deliberately broken domain, dnssec-failed.org, which it must refuse. It only protects domains that are signed, but it has no downside.
What is ECS, and why isn't it shown here?
ECS (EDNS Client Subnet) means a resolver passes part of your IP address on to a site's DNS servers, so a CDN can pick a server near you rather than near the resolver. Downloads and video can be faster, at the cost of revealing a little about where you are.
It isn't shown because it isn't fixed: in our checks, the same resolver passed it on from some places and over some protocols but not others. A single yes or no would mislead you.
Why aren't 114DNS or Baidu DNS here?
They only offer plain DNS, and their servers don't answer HTTPS at all, so a browser has no way to reach them. Quad101 (Taiwan, China) isn't included either: its DoH didn't answer from other regions when we checked.
Do you collect my data?
No. The queries go straight from your browser to each resolver, and they're for popular public sites and random names; nothing about you is in them. Your results stay in your browser. Only when you click Share are they written into the share link (each resolver's times, no IP address; including your country or region is up to you).
As with any DNS query, each resolver sees your IP address, and its own privacy policy applies. The code is open source on GitHub.