Find a provider and read its listed primary and secondary DNS addresses. Confirm the provider’s current setup instructions before changing your network settings.
Runs locally in your browser| Service provider | dns1 | dns2 |
|---|---|---|
| Alibaba AliDNS | 223.5.5.5 | 223.6.6.6 |
| Baidu DNS | 180.76.76.76 | 2400:da00::6666(ipv6) |
| OpenDNS | 208.67.222.222 | 208.67.220.220 |
| 8.8.8.8 | 8.8.4.4 | |
| 114 DNS | 114.114.114.114 | 114.114.115.115 |
| Cloudflare | 1.1.1.1 | 1.0.0.1 |
| Quad9 | 9.9.9.9 | 149.112.112.112 |
| DNSPod | 119.29.29.29 | 182.254.116.116 |
| CNNIC sDNS | 1.2.4.8 | 210.2.4.8 |
| OneDNS | 117.50.11.11 | 117.50.22.22 |
| Yandex DNS | 77.88.8.8 | 77.88.8.1 |
| dnspai (carrier resolvers) | China Telecom: 101.226.4.6 China Unicom: 123.125.81.6 China Mobile: 101.226.4.6 China Tietong: 101.226.4.6 | |
The addresses above are the pairs each provider publishes for public use. The first address in each pair is normally configured as the primary resolver and the second as the fallback.
A slow or untrustworthy resolver makes every lookup, and therefore every page load, feel slower. A resolver that has been tampered with can also redirect you to advertising pages, block sites you asked for, or log every name you look up. The addresses here are published by the providers themselves; confirm the current pair on the provider's own documentation before committing them to a router or a DNS configuration file.
This page is a reference table of public recursive resolver addresses, not a lookup tool. Use it to choose a primary and a secondary DNS server before changing the settings on a router, a laptop or a server. To run a query against a domain name instead, use the DNS record explorer, which resolves A, AAAA, MX, TXT, CNAME and NS records.
The table collects providers that publish their addresses for public use: Google, Cloudflare, Quad9, OpenDNS and Yandex globally, plus AliDNS, Baidu, DNSPod, 114DNS, CNNIC sDNS, OneDNS and the resolver addresses published by the Chinese carriers for users in mainland China.
A recursive resolver answers the question your device asks: it walks the DNS hierarchy from the root down to the authoritative name server for the domain and returns the record. By default your device uses the resolver operated by your internet provider; changing it to a public resolver replaces that operator with another one.
A public resolver does not encrypt your browsing, hide your traffic from your provider, or make you anonymous. The resolver operator can see every name you look up, which is why a published privacy policy matters. Your provider still sees which IP addresses you connect to, unless you also use DNS over HTTPS or DNS over TLS together with encrypted transport such as ECH.
Latency differences between major providers are usually a few milliseconds and depend on where you are, because all of them run anycast networks that answer from the nearest location. The larger differences come from filtering policy and from whether the resolver is close to the content you use. Measure before you switch rather than trusting a ranking.
Several providers publish filtered variants on neighbouring addresses: Quad9 blocks known malicious domains on 9.9.9.9 and offers an unfiltered service on 9.9.9.10, Cloudflare's 1.1.1.2 and 1.1.1.3 add malware and adult-content filtering, and OpenDNS FamilyShield on 208.67.222.123 blocks adult content. The filtering is a policy decision, so read the provider's description of what is blocked before relying on it.
dns1 and dns2 are the two addresses a provider publishes for general use; the second is not a different service, only a second address for failover. Entries shown as IPv6 addresses, such as 2400:da00::6666, only work on a network that actually has IPv6 connectivity.
The carrier entries, where a single row lists several addresses for China Telecom, China Unicom, China Mobile and China Tietong, are different: those are ISP-operated resolvers that are fast from inside that network and often unreachable from outside it. A provider that publishes only a pair of addresses is almost always running an anycast network, so the same address is answered by whichever location is nearest to you rather than by one fixed data centre.
No user input; the page outputs a browsable list of public DNS server addresses from providers such as Google, Cloudflare, OpenDNS, AliDNS, and DNSPod.
Selecting a public resolver address when setting up a new device; comparing known provider DNS options before changing network configuration; checking published addresses for troubleshooting resolver issues.
The interactive DNS server list computation runs in browser JavaScript; the displayed list content used as its working input is not uploaded to VoriTools.
The page provides addresses only; it does not perform live DNS lookups or verify resolver reachability, response time, or behavior from the user's network.
For a neutral, no-logging resolver, Cloudflare on 1.1.1.1 and 1.0.0.1 is the usual choice. For the widest availability, Google on 8.8.8.8 and 8.8.4.4. For malware blocking, Quad9 on 9.9.9.9. In mainland China, AliDNS on 223.5.5.5 or DNSPod on 119.29.29.29 will usually answer domestic names faster than an overseas resolver.
It depends on your network. Both run anycast, so the answer comes from a nearby data centre, and the difference is often a few milliseconds. Run a query against each address and compare the reported query time rather than relying on published benchmarks.
No. It changes which company can see your lookups, not whether they can be seen. Your internet provider still observes the connections you open, and the resolver you switch to observes your queries. DNS over HTTPS or DNS over TLS hides queries from the network path, but the resolver operator still sees them.
In almost every operating system the secondary address is used only when the primary does not answer. It is not a load-balancing pair, so there is no benefit to choosing two servers from different providers for speed; the reason to set both is resilience.
Some networks, particularly hotel, campus and some national networks, intercept or block outbound DNS on port 53 to third-party resolvers. The usual workaround is DNS over HTTPS, which travels inside an ordinary HTTPS connection and is therefore much harder to block selectively.
Only if your network has working IPv6 connectivity. Adding an IPv6 resolver address on an IPv4-only connection gives you a server that never answers, which slows down every lookup while the client waits for the timeout.