Public DNS resolver · Cloudflare
Cloudflare 1.1.1.1 DNS servers
Cloudflare 1.1.1.1 answers on 1.1.1.1 and 1.0.0.1, with DNS over HTTPS at https://cloudflare-dns.com/dns-query. In our 2026-09-24 test it validated DNSSEC and sent no client subnet.
- Addresses
- 12
- Variants
- 3
- Measured
- 2026-09-24
- Operator
- Cloudflare
- Primary IPv4
- 1.1.1.1
- All IPv4
- 1.1.1.1, 1.0.0.1, 1.1.1.2, 1.0.0.2, 1.1.1.3, 1.0.0.3
- All IPv6
- 2606:4700:4700::1111, 2606:4700:4700::1001, 2606:4700:4700::1112, 2606:4700:4700::1002, 2606:4700:4700::1113, 2606:4700:4700::1003
- DNS over HTTPS
- https://cloudflare-dns.com/dns-query
- DNS over TLS
- one.one.one.one
- Service variants
- 3 (1.1.1.1; 1.1.1.1 for Families: malware; 1.1.1.1 for Families: malware and adult)
- DNSSEC in our test
- Validates
- Client subnet (ECS)
- None sent
- Protocols
- DNS (53), DoT, DoH
Cloudflare 1.1.1.1 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 |
|---|---|---|---|---|
| 1.1.1.1 | None | 1.1.1.11.0.0.1 | 2606:4700:4700::11112606:4700:4700::1001 | DoH https://cloudflare-dns.com/dns-queryDoT one.one.one.one |
| 1.1.1.1 for Families: malware | Malware | 1.1.1.21.0.0.2 | 2606:4700:4700::11122606:4700:4700::1002 | Not documented |
| 1.1.1.1 for Families: malware and adult | Malware and adult content | 1.1.1.31.0.0.3 | 2606:4700:4700::11132606:4700:4700::1003 | Not documented |
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)
- No client subnet reached the authoritative server from any address we probed.
- 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://cloudflare-dns.com/dns-query | Answered |
| DoT | one.one.one.one | 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 |
|---|---|---|
| AS13335 | CLOUDFLARENET - Cloudflare, Inc. | Announces the service addresses |
| AS13335 | CLOUDFLARENET - Cloudflare, Inc. | Queried from, in our probe |
Operator statements
Quoted from the operator's pages and checked word for word. We have not audited these practices.
“A Public Resolver user's IP address (referred to as the client or source IP address) will not be stored in non-volatile storage.”
“Cloudflare will delete the truncated IP address within 25 hours.”
“Cloudflare will not sell or share Public Resolver users' personal data with third parties or use personal data from the Public Resolver to target any user with advertisements.”
Confirm your device is using Cloudflare 1.1.1.1
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 @1.1.1.1
# Does it pass your subnet on (ECS)?
dig +short TXT o-o.myaddr.l.google.com @1.1.1.1
# Does it validate DNSSEC? SERVFAIL means yes
dig dnssec-failed.org @1.1.1.1Behind 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.
Cloudflare 1.1.1.1 questions
- What are Cloudflare 1.1.1.1's DNS server addresses?
- 1.1.1.1: 1.1.1.1, 1.0.0.1, 2606:4700:4700::1111, 2606:4700:4700::1001. 1.1.1.1 for Families: malware: 1.1.1.2, 1.0.0.2, 2606:4700:4700::1112, 2606:4700:4700::1002. 1.1.1.1 for Families: malware and adult: 1.1.1.3, 1.0.0.3, 2606:4700:4700::1113, 2606:4700:4700::1003.
- Does Cloudflare 1.1.1.1 validate DNSSEC?
- Yes. On 2026-09-24 every Cloudflare 1.1.1.1 address that answered returned SERVFAIL for three deliberately mis-signed domains while resolving ordinary names.
- Does Cloudflare 1.1.1.1 support DNS over HTTPS or DNS over TLS?
- DoH: https://cloudflare-dns.com/dns-query. DoT: one.one.one.one. 2 of 2 answered our test query on 2026-09-24.
- Does Cloudflare 1.1.1.1 send my IP subnet to other servers (ECS)?
- We observed no client subnet on any address we probed.
- How can I check that I am using Cloudflare 1.1.1.1?
- Run a DNS leak test and compare the network it reports with the one Cloudflare 1.1.1.1 queried from in our probe (AS13335). On the command line, dig +short whoami.akamai.net @1.1.1.1 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.