Google Public DNS answers on 8.8.8.8 and 8.8.4.4. It validates DNSSEC, filters nothing beyond rare legally required blocks, and passes part of your address (a /24) to authoritative servers so that they can pick a nearby server. Its full logs, with your IP, are deleted within 24–48 hours. A changed record can be flushed from its cache on Google’s own page.
| Service | Addresses |
|---|---|
| Google Public DNS | 8.8.8.88.8.4.42001:2001: |
| DNS64, for IPv6-only networks | 2001:2001: |
| Run by | Google (United States) |
| DNS over HTTPS | https://dns.google/dns-query |
| DNS over TLS | dns.google |
| Validates DNSSEC | Yes — a record whose signature fails validation is not returned |
| Sends your subnet (ECS) | Yes — authoritative servers see part of your address, for nearer answers |
| Blocks | Nothing, except domains a court or law requires it to block in some countries |
| Logs | Your IP for 24–48 hours; then city-level data only |
| Flush its cache | developers.google.com/speed/public-dns/cache |
What does Google Public DNS answer for your domain?
Enter a hostname: we ask Google Public DNS and the domain’s own nameservers, and show whether its cached copy is up to date — and if not, how long until it asks again.
Encrypted DNS
DNS over HTTPS at https://dns.google/dns-query (RFC 8484, GET and POST), a JSON API at https://dns.google/resolve, and DNS over TLS to dns.google on port 853.
What it blocks
Google “does not perform blocking or filtering of any kind, except for certain domains in rare cases”: names it is legally required to block — in Belgium, France, India, Italy and Portugal, among others — get REFUSED, optionally with extended DNS error 16 (Censored). A name that does not exist always gets a plain NXDOMAIN.
What it logs
Temporary logs hold your IP address and the query and are “subject to our deletion processes within 24-48 hours”; permanent logs drop the IP and keep city or region-level location. Google says it does not correlate these logs with other Google services, except to deal with security and abuse.
It passes the first 24 bits of an IPv4 address (56 of an IPv6 one) to authoritative servers that support EDNS Client Subnet, so that they can answer with a server near you.
Flushing its cache
Google’s Flush Cache page clears one name and record type from its cache, so its next answer comes fresh from your nameservers. Google notes that names answered with EDNS Client Subnet cannot be flushed.
Worth knowing
- A client sending more than about 1,000–1,500 queries a second from one address may be rate-limited — Google’s pages give both figures.
- To check you are using it: dig TXT test.dns.google.com @dns.google returns “Thanks for using Google Public DNS.”
Sources
Checked on 27 September 2026 against these official sources:
- Get Started — Public DNS — developers.google.com
- DNS-over-HTTPS (DoH) — developers.google.com
- Frequently Asked Questions — developers.google.com
- Your Privacy — developers.google.com
- Blocking Behavior — developers.google.com
- Flush Cache — Public DNS — developers.google.com
- Troubleshooting — developers.google.com