DNS resolver registry · 114DNS

114DNS DNS servers

114DNS offers 3 service variants with different filtering, reachable over DNS (53). Every address and endpoint below is taken from the operator's documentation; the behaviour is what we measured on 2026-09-24.
114.114.114.114
primary address
6
addresses in 3 variants
Does not validate
DNSSEC in our test
None sent
client subnet (ECS)

Addresses

114DNS DNS addresses by variant

Set the IPv4 or IPv6 addresses as your DNS servers, or use an encrypted endpoint where one is listed.

114DNS public

Not specified by the operator

IPv4
114.114.114.114
114.114.115.115

114DNS safe

Phishing, virus and trojan sites

IPv4
114.114.114.119no answer in our probe
114.114.115.119no answer in our probe

114DNS family

Pornographic sites

IPv4
114.114.114.110no answer in our probe
114.114.115.110no answer in our probe

Measured

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. How we test

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.

Encrypted endpoints

None documented on the page we checked.

Networks

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.

Announcing the service addresses

  • AS21859 ZEN-ECN - Zenlayer Inc
  • AS137702 CHINATELECOM-JIANGSU-NANJING-IDC - Nanjing, Jiangsu Province, P.R.China.

Queried from, in our probe

Not published: the lookup did not return, or the network describes our vantage point rather than the resolver.

Check it

Confirm your device is using 114DNS

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.

From a terminal

# 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.114

Behind 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.

Questions

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

Sources and dates

Documentation checked 2026-09-24. Measured 2026-09-24. Registry reviewed 2026-09-24.