Public DNS resolver · Cisco
OpenDNS DNS servers
OpenDNS (run by Cisco) answers on 208.67.222.222 and 208.67.220.220. In our 2026-09-24 test it validated DNSSEC and sent a /24 client subnet to authoritative servers.
- Addresses
- 4
- Variants
- 2
- Measured
- 2026-09-24
- Operator
- Cisco
- Primary IPv4
- 208.67.222.222
- All IPv4
- 208.67.222.222, 208.67.220.220, 208.67.222.123, 208.67.220.123
- All IPv6
- none documented
- DNS over HTTPS
- not documented
- DNS over TLS
- not documented
- Service variants
- 2 (OpenDNS Home; OpenDNS FamilyShield)
- DNSSEC in our test
- Validates
- Client subnet (ECS)
- Sends /24
- Protocols
- DNS (53)
OpenDNS 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 |
|---|---|---|---|---|
| OpenDNS Home | Not described on the operator setup page | 208.67.222.222208.67.220.220 | Not documented | |
| OpenDNS FamilyShield | Not described on the operator setup page | 208.67.222.123208.67.220.123 | 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)
- 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
- 4/4 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.
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 |
|---|---|---|
| AS36692 | CISCO-UMBRELLA - Cisco OpenDNS, LLC | Announces the service addresses |
| AS36692 | CISCO-UMBRELLA - Cisco OpenDNS, 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.
“OpenDNS is now part of Cisco”
Confirm your device is using OpenDNS
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 @208.67.222.222
# Does it pass your subnet on (ECS)?
dig +short TXT o-o.myaddr.l.google.com @208.67.222.222
# Does it validate DNSSEC? SERVFAIL means yes
dig dnssec-failed.org @208.67.222.222Behind 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.
OpenDNS questions
- What are OpenDNS's DNS server addresses?
- OpenDNS Home: 208.67.222.222, 208.67.220.220. OpenDNS FamilyShield: 208.67.222.123, 208.67.220.123.
- Does OpenDNS validate DNSSEC?
- Yes. On 2026-09-24 every OpenDNS address that answered returned SERVFAIL for three deliberately mis-signed domains while resolving ordinary names.
- Does OpenDNS support DNS over HTTPS or DNS over TLS?
- The OpenDNS page we checked documents plain DNS addresses only.
- Does OpenDNS 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 OpenDNS?
- Run a DNS leak test and compare the network it reports with the one OpenDNS queried from in our probe (AS36692). On the command line, dig +short whoami.akamai.net @208.67.222.222 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.