Public DNS resolver · Quad9
Quad9 DNS servers
Quad9 answers on 9.9.9.9 and 149.112.112.112, with DNS over HTTPS at https://dns.quad9.net/dns-query. In our 2026-09-24 test it validated DNSSEC and sent a /24 client subnet to authoritative servers.
- Addresses
- 12
- Variants
- 3
- Measured
- 2026-09-24
- Operator
- Quad9
- Primary IPv4
- 9.9.9.9
- All IPv4
- 9.9.9.9, 149.112.112.112, 9.9.9.11, 149.112.112.11, 9.9.9.10, 149.112.112.10
- All IPv6
- 2620:fe::fe, 2620:fe::9, 2620:fe::11, 2620:fe::fe:11, 2620:fe::10, 2620:fe::fe:10
- DNS over HTTPS
- https://dns.quad9.net/dns-query, https://dns11.quad9.net/dns-query, https://dns10.quad9.net/dns-query
- DNS over TLS
- dns.quad9.net, dns11.quad9.net, dns10.quad9.net
- Service variants
- 3 (Quad9 (recommended); Quad9 secured with ECS; Quad9 unsecured)
- DNSSEC in our test
- Validates
- Client subnet (ECS)
- Some addresses send /24
- Protocols
- DNS (53), DoT, DoH
- Jurisdiction (stated)
- Quad9 c/o SWITCH Werdstrasse 2 8004 Zürich Switzerland
Quad9 DNS addresses by variant
Set the IPv4 or IPv6 addresses as your DNS servers, or use an encrypted endpoint where one is listed.
| Variant | Filtering (operator description) | IPv4 | IPv6 | Encrypted |
|---|---|---|---|---|
| Quad9 (recommended) | Malware blocking | 9.9.9.9149.112.112.112 | 2620:fe::fe2620:fe::9 | DoH https://dns.quad9.net/dns-queryDoT dns.quad9.net |
| Quad9 secured with ECS | Malware blocking | 9.9.9.11149.112.112.11 | 2620:fe::112620:fe::fe:11 | DoH https://dns11.quad9.net/dns-queryDoT dns11.quad9.net |
| Quad9 unsecured | None | 9.9.9.10149.112.112.10 | 2620:fe::102620:fe::fe:10 | DoH https://dns10.quad9.net/dns-queryDoT dns10.quad9.net |
What we observed
Measured 2026-09-24 from one vantage point, three rounds per address, majority result. Anycast resolvers can behave differently from other networks.
- DNSSEC validation
- Validates Returned SERVFAIL for dnssec-failed.org, rhybar.cz and badsig.go.dnscheck.tools on every address that answered, while resolving example.com.
- Client subnet (ECS)
- Some addresses send /24. The authoritative server received that much of the client address, enough to locate a user to a block of addresses.
- Plain DNS and NXDOMAIN
- 6/6 documented IPv4 addresses answered on port 53. Random non-existent names came back as NXDOMAIN, so errors are not rewritten into ads or search pages.
| Protocol | Endpoint | Our test query |
|---|---|---|
| DoH | https://dns.quad9.net/dns-query | Answered |
| DoH | https://dns11.quad9.net/dns-query | Answered |
| DoH | https://dns10.quad9.net/dns-query | Answered |
| DoT | dns.quad9.net | Answered |
| DoT | dns11.quad9.net | Answered |
| DoT | dns10.quad9.net | Answered |
Which networks carry it
The announcing network comes from RIPEstat routing data for each documented address. The query network is where the resolver sent its own lookups during our probe, which a DNS leak test reports.
| ASN | Holder | Role |
|---|---|---|
| AS19281 | QUAD9-AS-1 - Quad9 | Announces the service addresses |
Query network not published: the lookup did not return, or the network describes our vantage point rather than the resolver.
Operator statements
Quoted from the operator's pages and checked word for word. We have not audited these practices.
Confirm your device is using Quad9
Changing a DNS setting does not guarantee your lookups reach that resolver: a VPN, a browser's own secure DNS or a proxy can send them elsewhere. Our DNS leak test shows which resolvers actually received your queries.
# Which address did the resolver query from?
dig +short whoami.akamai.net @9.9.9.9
# Does it pass your subnet on (ECS)?
dig +short TXT o-o.myaddr.l.google.com @9.9.9.9
# Does it validate DNSSEC? SERVFAIL means yes
dig dnssec-failed.org @9.9.9.9Behind a proxy
With an HTTP proxy, or a client set to socks5h://, the proxy side resolves hostnames, so your own resolver setting does not apply to that traffic. With socks5:// in curl or Python requests, your device resolves names first. The SOCKS5 vs SOCKS5h guide shows how to check which one you have.
Quad9 questions
- What are Quad9's DNS server addresses?
- Quad9 (recommended): 9.9.9.9, 149.112.112.112, 2620:fe::fe, 2620:fe::9. Quad9 secured with ECS: 9.9.9.11, 149.112.112.11, 2620:fe::11, 2620:fe::fe:11. Quad9 unsecured: 9.9.9.10, 149.112.112.10, 2620:fe::10, 2620:fe::fe:10.
- Does Quad9 validate DNSSEC?
- Yes. On 2026-09-24 every Quad9 address that answered returned SERVFAIL for three deliberately mis-signed domains while resolving ordinary names.
- Does Quad9 support DNS over HTTPS or DNS over TLS?
- DoH: https://dns.quad9.net/dns-query, https://dns11.quad9.net/dns-query, https://dns10.quad9.net/dns-query. DoT: dns.quad9.net, dns11.quad9.net, dns10.quad9.net. 6 of 6 answered our test query on 2026-09-24.
- Does Quad9 send my IP subnet to other servers (ECS)?
- Yes on at least one address: we observed a /24 client subnet reaching the authoritative server.
- How can I check that I am using Quad9?
- Run a DNS leak test and compare the network it reports. On the command line, dig +short whoami.akamai.net @9.9.9.9 returns the address the resolver used to query Akamai.
Sources
Documentation checked 2026-09-24. Measured 2026-09-24. Registry reviewed 2026-09-24.
Addresses and endpoints come from each operator's documentation; behaviour is what we measured from one location on 2026-09-24. Speed, uptime and how well a filter blocks what it promises were not tested.