Public DNS resolver · Google
Google Public DNS DNS servers
Google Public DNS answers on 8.8.8.8 and 8.8.4.4, with DNS over HTTPS at https://dns.google/dns-query. In our 2026-09-24 test it validated DNSSEC and sent a /24 client subnet to authoritative servers.
- Addresses
- 4
- Variants
- 1
- Measured
- 2026-09-24
- Operator
- Primary IPv4
- 8.8.8.8
- All IPv4
- 8.8.8.8, 8.8.4.4
- All IPv6
- 2001:4860:4860::8888, 2001:4860:4860::8844
- DNS over HTTPS
- https://dns.google/dns-query
- DNS over TLS
- dns.google
- Service variants
- 1 (Google Public DNS)
- DNSSEC in our test
- Validates
- Client subnet (ECS)
- Sends /24
- Protocols
- DNS (53), DoT, DoH
Google Public DNS 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 |
|---|---|---|---|---|
| Google Public DNS | Not specified by the operator | 8.8.8.88.8.4.4 | 2001:4860:4860::88882001:4860:4860::8844 | DoH https://dns.google/dns-queryDoT dns.google |
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)
- 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
- 2/2 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.google/dns-query | Answered |
| DoT | dns.google | 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 |
|---|---|---|
| AS15169 | GOOGLE - Google LLC | Announces the service addresses |
| AS15169 | GOOGLE - Google LLC | Queried from, in our probe |
Operator statements
Quoted from the operator's pages and checked word for word. We have not audited these practices.
“Temporary logs are the only logs that store both your IP address and your DNS query.”
“The permanent logs are a sampling of the temporary logs where your IP address is removed and replaced by a city or region-level location.”
Confirm your device is using Google Public DNS
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 @8.8.8.8
# Does it pass your subnet on (ECS)?
dig +short TXT o-o.myaddr.l.google.com @8.8.8.8
# Does it validate DNSSEC? SERVFAIL means yes
dig dnssec-failed.org @8.8.8.8Behind 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.
Google Public DNS questions
- What are Google Public DNS's DNS server addresses?
- Google Public DNS: 8.8.8.8, 8.8.4.4, 2001:4860:4860::8888, 2001:4860:4860::8844.
- Does Google Public DNS validate DNSSEC?
- Yes. On 2026-09-24 every Google Public DNS address that answered returned SERVFAIL for three deliberately mis-signed domains while resolving ordinary names.
- Does Google Public DNS support DNS over HTTPS or DNS over TLS?
- DoH: https://dns.google/dns-query. DoT: dns.google. 2 of 2 answered our test query on 2026-09-24.
- Does Google Public 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 Google Public DNS?
- Run a DNS leak test and compare the network it reports with the one Google Public DNS queried from in our probe (AS15169). On the command line, dig +short whoami.akamai.net @8.8.8.8 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.