Public DNS resolver · AdGuard
AdGuard DNS DNS servers
AdGuard DNS answers on 94.140.14.14 and 94.140.15.15, with DNS over HTTPS at https://dns.adguard-dns.com/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
- AdGuard
- Primary IPv4
- 94.140.14.14
- All IPv4
- 94.140.14.14, 94.140.15.15, 94.140.14.15, 94.140.15.16, 94.140.14.140, 94.140.14.141
- All IPv6
- 2a10:50c0::ad1:ff, 2a10:50c0::ad2:ff, 2a10:50c0::bad1:ff, 2a10:50c0::bad2:ff, 2a10:50c0::1:ff, 2a10:50c0::2:ff
- DNS over HTTPS
- https://dns.adguard-dns.com/dns-query, https://family.adguard-dns.com/dns-query, https://unfiltered.adguard-dns.com/dns-query
- DNS over TLS
- dns.adguard-dns.com, family.adguard-dns.com, unfiltered.adguard-dns.com
- Service variants
- 3 (AdGuard DNS default; AdGuard DNS family protection; AdGuard DNS non-filtering)
- DNSSEC in our test
- Validates
- Client subnet (ECS)
- Sends /24
- Protocols
- DNS (53), DoT, DoH
- Jurisdiction (stated)
- ADGUARD SOFTWARE LIMITED is a company registered in Limassol, Cyprus
AdGuard DNS DNS addresses by variant
| Variant | Filtering (operator description) | IPv4 | IPv6 | Encrypted |
|---|---|---|---|---|
| AdGuard DNS default | Ads, tracking and phishing | 94.140.14.1494.140.15.15 | 2a10:50c0::ad1:ff2a10:50c0::ad2:ff | DoH https://dns.adguard-dns.com/dns-queryDoT dns.adguard-dns.com |
| AdGuard DNS family protection | Default filtering, adult websites and safe search | 94.140.14.1594.140.15.16 | 2a10:50c0::bad1:ff2a10:50c0::bad2:ff | DoH https://family.adguard-dns.com/dns-queryDoT family.adguard-dns.com |
| AdGuard DNS non-filtering | None | 94.140.14.14094.140.14.141 | 2a10:50c0::1:ff2a10:50c0::2:ff | DoH https://unfiltered.adguard-dns.com/dns-queryDoT unfiltered.adguard-dns.com |
What we observed
- 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)
- Sends /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.adguard-dns.com/dns-query | Answered |
| DoH | https://family.adguard-dns.com/dns-query | Answered |
| DoH | https://unfiltered.adguard-dns.com/dns-query | Answered |
| DoT | dns.adguard-dns.com | Answered |
| DoT | family.adguard-dns.com | Answered |
| DoT | unfiltered.adguard-dns.com | Answered |
Which networks carry it
| ASN | Holder | Role |
|---|---|---|
| AS212772 | ADGUARD AdGuard Software Limited | Announces the service addresses |
| AS60068 | CDN77 Datacamp Limited | Queried from, in our probe |
Operator statements
“ADGUARD SOFTWARE LIMITED is a company registered in Limassol, Cyprus”
“We keep and store an anonymous database of domains requested in the last 24 hours.”
Confirm your device is using AdGuard DNS
# Which address did the resolver query from?
dig +short whoami.akamai.net @94.140.14.14
# Does it pass your subnet on (ECS)?
dig +short TXT o-o.myaddr.l.google.com @94.140.14.14
# Does it validate DNSSEC? SERVFAIL means yes
dig dnssec-failed.org @94.140.14.14Behind 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.
AdGuard DNS questions
- What are AdGuard DNS's DNS server addresses?
- AdGuard DNS default: 94.140.14.14, 94.140.15.15, 2a10:50c0::ad1:ff, 2a10:50c0::ad2:ff. AdGuard DNS family protection: 94.140.14.15, 94.140.15.16, 2a10:50c0::bad1:ff, 2a10:50c0::bad2:ff. AdGuard DNS non-filtering: 94.140.14.140, 94.140.14.141, 2a10:50c0::1:ff, 2a10:50c0::2:ff.
- Does AdGuard DNS validate DNSSEC?
- Yes. On 2026-09-24 every AdGuard DNS address that answered returned SERVFAIL for three deliberately mis-signed domains while resolving ordinary names.
- Does AdGuard DNS support DNS over HTTPS or DNS over TLS?
- DoH: https://dns.adguard-dns.com/dns-query, https://family.adguard-dns.com/dns-query, https://unfiltered.adguard-dns.com/dns-query. DoT: dns.adguard-dns.com, family.adguard-dns.com, unfiltered.adguard-dns.com. 6 of 6 answered our test query on 2026-09-24.
- Does AdGuard DNS 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 AdGuard DNS?
- Run a DNS leak test and compare the network it reports with the one AdGuard DNS queried from in our probe (AS60068). On the command line, dig +short whoami.akamai.net @94.140.14.14 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.