Public DNS resolver · 114DNS
114DNS DNS servers
114DNS answers on 114.114.114.114 and 114.114.115.115. In our 2026-09-24 test it did not validate DNSSEC and sent no client subnet.
- Addresses
- 6
- Variants
- 3
- Measured
- 2026-09-24
- Operator
- 114DNS
- Primary IPv4
- 114.114.114.114
- All IPv4
- 114.114.114.114, 114.114.115.115, 114.114.114.119, 114.114.115.119, 114.114.114.110, 114.114.115.110
- All IPv6
- none documented
- DNS over HTTPS
- not documented
- DNS over TLS
- not documented
- Service variants
- 3 (114DNS public; 114DNS safe; 114DNS family)
- DNSSEC in our test
- Does not validate
- Client subnet (ECS)
- None sent
- Protocols
- DNS (53)
114DNS DNS addresses by variant
| Variant | Filtering (operator description) | IPv4 | IPv6 | Encrypted |
|---|---|---|---|---|
| 114DNS public | Not specified by the operator | 114.114.114.114114.114.115.115 | Not documented | |
| 114DNS safe | Phishing, virus and trojan sites | 114.114.114.119no answer in our probe114.114.115.119no answer in our probe | Not documented | |
| 114DNS family | Pornographic sites | 114.114.114.110no answer in our probe114.114.115.110no answer in our probe | Not documented |
What we observed
- DNSSEC validation
- Does not validate Returned addresses for dnssec-failed.org, rhybar.cz and badsig.go.dnscheck.tools, which a validating resolver would refuse.
- Client subnet (ECS)
- No client subnet reached the authoritative server from any address we probed.
- Plain DNS and NXDOMAIN
- 2/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.
Which networks carry it
| ASN | Holder | Role |
|---|---|---|
| AS21859 | ZEN-ECN - Zenlayer Inc | Announces the service addresses |
| AS137702 | CHINATELECOM-JIANGSU-NANJING-IDC - Nanjing, Jiangsu Province, P.R.China. | Announces the service addresses |
Query network not published: the lookup did not return, or the network describes our vantage point rather than the resolver.
Confirm your device is using 114DNS
# Which address did the resolver query from?
dig +short whoami.akamai.net @114.114.114.114
# Does it pass your subnet on (ECS)?
dig +short TXT o-o.myaddr.l.google.com @114.114.114.114
# Does it validate DNSSEC? SERVFAIL means yes
dig dnssec-failed.org @114.114.114.114Behind 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.
114DNS questions
- What are 114DNS's DNS server addresses?
- 114DNS public: 114.114.114.114, 114.114.115.115. 114DNS safe: 114.114.114.119, 114.114.115.119. 114DNS family: 114.114.114.110, 114.114.115.110.
- Does 114DNS validate DNSSEC?
- Not in our 2026-09-24 test: it returned addresses for all three deliberately mis-signed domains.
- Does 114DNS support DNS over HTTPS or DNS over TLS?
- The 114DNS page we checked documents plain DNS addresses only.
- Does 114DNS 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 114DNS?
- Run a DNS leak test and compare the network it reports. On the command line, dig +short whoami.akamai.net @114.114.114.114 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.