Public DNS server list

Public DNS server list

Public resolvers and Chinese carrier DNS by province, with official sources, purpose and live test results

Computed in your browser

Check the test node and time at the top, then search by name, province, carrier or IP; green badges mean the address resolved from this site’s test node.

About the test results

Test node
中国 福建 厦门 · 中国电信
Tested at
Method
TCP port 53, 3 rounds; queries www.baidu.com and a random .invalid name
IPv6
The test node has no IPv6 connectivity; IPv6 addresses were not tested
Summary
357 addresses: 81 resolved, 27 refused, 249 no response or error

Results only reflect this test node’s network at the time shown, and latency includes TCP connection setup, so treat it as a rough guide. Carrier DNS usually serves only its own subscribers, so no response from elsewhere does not mean failure. The test node’s network intercepts UDP 53, so this run used TCP; servers that answer only over UDP also show as no response. Confirm on your own network.

Public recursive DNS 18 entries · 58 addresses

Recursive resolvers offered to the public. Addresses listed on official pages show the check date; those found only in third-party directories or community lists are labeled separately.

Name and purpose IPv4 and result IPv6 and result Source
AliDNS Alibaba Cloud Plain resolution DoH https://dns.alidns.com/dns-query DoT dns.alidns.com
  • 223.5.5.5Resolves 3/3 rounds · 54 ms
  • 223.6.6.6Resolves 3/3 rounds · 54 ms
  • 2400:3200::1Not tested
  • 2400:3200:baba::1Not tested
Official source checked (2026-11-07) alidns.com
Tencent Public DNS (DNSPod) Tencent Cloud Plain resolution DoH https://doh.pub/dns-query DoT dot.pub
  • 119.29.29.29Answers, test lookup timed out
  • 2402:4e00::Not tested
  • 2402:4e00:1::Not tested
Official source checked (2026-11-07) cloud.tencent.com/document/product/302/110786
114DNS (standard) Nanjing Xinfeng Plain resolution
  • 114.114.114.114Resolves 3/3 rounds · 54 ms
  • 114.114.115.115Resolves 3/3 rounds · 54 ms
— Official source checked (2026-11-07) 114dns.com
Baidu Public DNS Baidu Plain resolution
  • 180.76.76.76No response
— Official source checked (2026-11-07) dudns.baidu.com
360 Secure DNS Qihoo 360 Plain resolution The official page labels 101.226.4.6 and 218.30.118.6 for China Telecom networks; 101.198.198.198 and 101.198.199.200 appear in its DoT example. DoH https://doh.360.cn/dns-query DoT dot.360.cn
  • 101.226.4.6Resolves 3/3 rounds · 43 ms
  • 218.30.118.6Resolves 3/3 rounds · 77 ms
  • 101.198.198.198Resolves 3/3 rounds · 46 ms
  • 101.198.199.200Resolves 3/3 rounds · 45 ms
— Official source checked (2026-11-07) sdns.360.net/dnsPublic.html
360 Secure DNS (China Unicom) Qihoo 360 Plain resolution The current 360 page lists only the China Telecom addresses; this Unicom pair comes from a third-party directory.
  • 123.125.81.6Resolves 3/3 rounds · 79 ms
  • 140.207.198.6No response
— Third-party directory (AdGuard DNS knowledge base, 2026-11-07) adguard-dns.io/kb/general/dns-providers
Volcengine PublicDNS (ByteDance) Volcengine Plain resolution
  • 180.184.1.1Resolves 3/3 rounds · 52 ms
  • 180.184.2.2Resolves 3/3 rounds · 51 ms
— Third-party directory (AdGuard DNS knowledge base, 2026-11-07) adguard-dns.io/kb/general/dns-providers
OneDNS (pure) ThreatBook Plain resolution
  • 117.50.10.10No response
  • 52.80.52.52No response
  • 2400:7fc0:849e:200::8Not tested
  • 2404:c2c0:85d8:901::8Not tested
Third-party directory (AdGuard DNS knowledge base, 2026-11-07) adguard-dns.io/kb/general/dns-providers
CNNIC SDNS CNNIC Plain resolution The official site is online but no longer lists these addresses, so current public availability cannot be confirmed.
  • 1.2.4.8Resolves 2/3 rounds · 3688 ms
  • 210.2.4.8Resolves 3/3 rounds · 82 ms
— Community list, not officially confirmed
Google Public DNS Google Plain resolution DoT dns.google
  • 8.8.8.8Resolves 3/3 rounds · 243 ms
  • 8.8.4.4Resolves 3/3 rounds · 235 ms
  • 2001:4860:4860::8888Not tested
  • 2001:4860:4860::8844Not tested
Official source checked (2026-11-07) developers.google.com/speed/public-dns/docs/using
Cloudflare 1.1.1.1 Cloudflare Plain resolution
  • 1.1.1.1Resolves 3/3 rounds · 153 ms
  • 1.0.0.1Resolves 3/3 rounds · 133 ms
  • 2606:4700:4700::1111Not tested
  • 2606:4700:4700::1001Not tested
Official source checked (2026-11-07) developers.cloudflare.com/1.1.1.1/ip-addresses
Quad9 (malware blocking) Quad9 Foundation Security filtering Quad9’s recommended addresses block known malicious domains by default; the unfiltered service is 9.9.9.10 and 149.112.112.10. DoH https://dns.quad9.net/dns-query DoT dns.quad9.net
  • 9.9.9.9Resolves 3/3 rounds · 484 ms
  • 149.112.112.112Resolves 3/3 rounds · 445 ms
  • 2620:fe::feNot tested
  • 2620:fe::9Not tested
Official source checked (2026-11-07) quad9.net/service/service-addresses-and-features
Quad9 (unsecured) Quad9 Foundation Plain resolution DoH https://dns10.quad9.net/dns-query DoT dns10.quad9.net
  • 9.9.9.10Resolves 3/3 rounds · 464 ms
  • 149.112.112.10Resolves 3/3 rounds · 512 ms
  • 2620:fe::10Not tested
  • 2620:fe::fe:10Not tested
Official source checked (2026-11-07) quad9.net/service/service-addresses-and-features
OpenDNS Cisco Plain resolution
  • 208.67.222.222Resolves 3/3 rounds · 762 ms
  • 208.67.220.220Resolves 3/3 rounds · 2245 ms
  • 2620:119:35::35Not tested
  • 2620:119:53::53Not tested
Third-party directory (AdGuard DNS knowledge base, 2026-11-07) adguard-dns.io/kb/general/dns-providers
DNS.SB Plain resolution
  • 185.222.222.222Resolves 3/3 rounds · 431 ms
  • 45.11.45.11Resolves 3/3 rounds · 400 ms
  • 2a09::Not tested
  • 2a11::Not tested
Official source checked (2026-11-07) dns.sb/guide
Oracle OCI recursive DNS (formerly Dyn) Oracle Plain resolution Oracle documents this recursive service as free for anyone and DNSSEC-validating.
  • 216.146.35.35Resolves 3/3 rounds · 1367 ms
  • 216.146.36.36Resolves 3/3 rounds · 1353 ms
— Official source checked (2026-11-07) docs.oracle.com/en-us/iaas/Content/DNS/Concepts/recursive-dns.htm
Quad101 (TWNIC) TWNIC Plain resolution
  • 101.101.101.101No response
  • 101.102.103.104Resolves 3/3 rounds · 235 ms
  • 2001:de4::101Not tested
  • 2001:de4::102Not tested
Third-party directory (AdGuard DNS knowledge base, 2026-11-07) adguard-dns.io/kb/general/dns-providers
Verisign Public DNS Verisign Plain resolution Mislabeled on the reference site as a Swiss bank. No current Verisign service page was found; only a third-party directory still lists it, so rely on test results.
  • 64.6.64.6Resolves 3/3 rounds · 391 ms
  • 64.6.65.6Resolves 3/3 rounds · 381 ms
  • 2620:74:1b::1:1Not tested
  • 2620:74:1c::2:2Not tested
Third-party directory (AdGuard DNS knowledge base, 2026-11-07) adguard-dns.io/kb/general/dns-providers
Filtering and security DNS 11 entries · 36 addresses

Block malicious, adult or advertising domains according to the provider’s rules. Blocked sites will not load, so these are not suitable as plain resolvers when troubleshooting.

Name and purpose IPv4 and result IPv6 and result Source
114DNS (security) Nanjing Xinfeng Security filtering Blocks phishing, virus and trojan sites.
  • 114.114.114.119Resolves 3/3 rounds · 51 ms
  • 114.114.115.119Resolves 3/3 rounds · 50 ms
— Official source checked (2026-11-07) 114dns.com
114DNS (family) Nanjing Xinfeng Family filtering Adds adult-content blocking.
  • 114.114.114.110Resolves 3/3 rounds · 48 ms
  • 114.114.115.110Resolves 3/3 rounds · 51 ms
— Official source checked (2026-11-07) 114dns.com
Cloudflare (malware blocking) Cloudflare Security filtering
  • 1.1.1.2Resolves 3/3 rounds · 134 ms
  • 1.0.0.2Resolves 3/3 rounds · 141 ms
  • 2606:4700:4700::1112Not tested
  • 2606:4700:4700::1002Not tested
Official source checked (2026-11-07) developers.cloudflare.com/1.1.1.1/ip-addresses
Cloudflare for Families Cloudflare Family filtering Blocks malware and adult content.
  • 1.1.1.3Resolves 3/3 rounds · 146 ms
  • 1.0.0.3Resolves 3/3 rounds · 144 ms
  • 2606:4700:4700::1113Not tested
  • 2606:4700:4700::1003Not tested
Official source checked (2026-11-07) developers.cloudflare.com/1.1.1.1/ip-addresses
OpenDNS FamilyShield Cisco Family filtering
  • 208.67.222.123Resolves 3/3 rounds · 2588 ms
  • 208.67.220.123Resolves 3/3 rounds · 548 ms
— Third-party directory (AdGuard DNS knowledge base, 2026-11-07) adguard-dns.io/kb/general/dns-providers
CleanBrowsing Security Filter CleanBrowsing Security filtering
  • 185.228.168.9Resolves 3/3 rounds · 453 ms
  • 185.228.169.9Resolves 3/3 rounds · 400 ms
  • 2a0d:2a00:1::2Not tested
  • 2a0d:2a00:2::2Not tested
Official source checked (2026-11-07) cleanbrowsing.org/filters
CleanBrowsing Adult Filter CleanBrowsing Adult-content filtering Mislabeled on the reference site as a California resolver. Adult sites are blocked, so it is not a general-purpose resolver.
  • 185.228.168.10Resolves 3/3 rounds · 416 ms
  • 185.228.169.11Resolves 3/3 rounds · 361 ms
  • 2a0d:2a00:1::1Not tested
  • 2a0d:2a00:2::1Not tested
Official source checked (2026-11-07) cleanbrowsing.org/filters
CleanBrowsing Family Filter CleanBrowsing Family filtering
  • 185.228.168.168Resolves 3/3 rounds · 406 ms
  • 185.228.169.168Resolves 3/3 rounds · 366 ms
  • 2a0d:2a00:1::Not tested
  • 2a0d:2a00:2::Not tested
Official source checked (2026-11-07) cleanbrowsing.org/filters
AdGuard DNS (default) AdGuard Ad filtering Blocks ads, trackers and phishing by default, which can break some site features; the unfiltered version is 94.140.14.140 and 94.140.14.141.
  • 94.140.14.14Resolves 3/3 rounds · 475 ms
  • 94.140.15.15Resolves 3/3 rounds · 378 ms
  • 2a10:50c0::ad1:ffNot tested
  • 2a10:50c0::ad2:ffNot tested
Third-party directory (AdGuard DNS knowledge base, 2026-11-07) adguard-dns.io/kb/general/dns-providers
OneDNS (block) ThreatBook Security filtering
  • 52.80.66.66No response
  • 117.50.22.22No response
  • 2400:7fc0:849e:200::4Not tested
  • 2404:c2c0:85d8:901::4Not tested
Third-party directory (AdGuard DNS knowledge base, 2026-11-07) adguard-dns.io/kb/general/dns-providers
OneDNS (family) ThreatBook Family filtering
  • 117.50.60.30No response
  • 52.80.60.30No response
— Third-party directory (AdGuard DNS knowledge base, 2026-11-07) adguard-dns.io/kb/general/dns-providers
China Telecom · carrier DNS 29 entries · 77 addresses

Carrier DNS addresses by province from community lists, as carriers do not publish a single official list. They usually serve only subscribers on that carrier in the same province; use and test them there.

Name and purpose IPv4 and result IPv6 and result Source
China Telecom IPv6 Plain resolution —
  • 240e:4c:4008::1Not tested
  • 240e:4c:4808::1Not tested
Community list, not officially confirmed
Beijing China Telecom Plain resolution
  • 219.141.136.10Refused
  • 219.141.140.10Refused
— Community list, not officially confirmed
Shanghai China Telecom Plain resolution
  • 202.96.209.133No response
  • 116.228.111.118No response
  • 202.96.209.5No response
  • 180.168.255.118No response
  • 203.62.139.69No response
  • 202.96.199.133No response
— Community list, not officially confirmed
Tianjin China Telecom Plain resolution
  • 219.150.32.132No response
  • 219.146.0.132No response
— Community list, not officially confirmed
Chongqing China Telecom Plain resolution
  • 61.128.192.68No response
  • 61.128.128.68No response
— Community list, not officially confirmed
Anhui China Telecom Plain resolution
  • 61.132.163.68Resolves 3/3 rounds · 50 ms
  • 202.102.213.68Resolves 3/3 rounds · 51 ms
  • 202.102.192.68Resolves 3/3 rounds · 50 ms
— Community list, not officially confirmed
Fujian China Telecom Plain resolution
  • 218.85.152.99Resolves 3/3 rounds · 386 ms
  • 218.85.157.99Resolves 3/3 rounds · 365 ms
— Community list, not officially confirmed
Gansu China Telecom Plain resolution
  • 202.100.64.68No response
  • 61.178.0.93No response
— Community list, not officially confirmed
Guangdong China Telecom Plain resolution
  • 202.96.128.86No response
  • 202.96.128.166No response
  • 202.96.134.133No response
  • 202.96.128.68No response
  • 202.96.154.8No response
  • 202.96.154.15No response
— Community list, not officially confirmed
Guangxi China Telecom Plain resolution
  • 202.103.225.68No response
  • 202.103.224.68No response
— Community list, not officially confirmed
Guizhou China Telecom Plain resolution
  • 202.98.192.67No response
  • 202.98.198.167No response
— Community list, not officially confirmed
Henan China Telecom Plain resolution
  • 222.88.88.88No response
  • 222.85.85.85No response
  • 219.150.150.150No response
  • 222.88.93.126No response
— Community list, not officially confirmed
Heilongjiang China Telecom Plain resolution
  • 219.147.198.230No response
  • 219.147.198.242No response
  • 112.100.100.100No response
— Community list, not officially confirmed
Hubei China Telecom Plain resolution
  • 202.103.24.68Resolves 2/3 rounds · 50 ms
  • 202.103.0.68No response
  • 202.103.44.150No response
  • 219.140.192.118No response
— Community list, not officially confirmed
Hunan China Telecom Plain resolution
  • 59.51.78.211No response
  • 59.51.78.210No response
  • 222.246.129.80No response
  • 222.246.129.81No response
— Community list, not officially confirmed
Jiangsu China Telecom Plain resolution
  • 218.2.2.2No response
  • 218.4.4.4No response
  • 61.147.37.1No response
  • 218.2.135.1No response
— Community list, not officially confirmed
Jiangxi China Telecom Plain resolution
  • 202.101.224.69No response
  • 202.101.226.68No response
  • 202.101.226.69No response
— Community list, not officially confirmed
Inner Mongolia China Telecom Plain resolution
  • 219.148.162.31No response
  • 222.74.39.50No response
  • 222.74.1.200No response
— Community list, not officially confirmed
Shandong China Telecom Plain resolution
  • 219.146.1.66No response
  • 219.147.1.66No response
— Community list, not officially confirmed
Shanxi China Telecom Plain resolution
  • 59.49.49.49No response
— Community list, not officially confirmed
Shaanxi China Telecom Plain resolution
  • 218.30.19.40No response
  • 61.134.1.4No response
— Community list, not officially confirmed
Sichuan China Telecom Plain resolution
  • 61.139.2.69No response
  • 218.6.200.139No response
— Community list, not officially confirmed
Yunnan China Telecom Plain resolution
  • 222.172.200.68No response
  • 61.166.150.123No response
— Community list, not officially confirmed
Zhejiang China Telecom Plain resolution
  • 202.101.172.35No response
  • 202.101.172.47No response
  • 61.153.81.75No response
  • 61.153.177.196No response
  • 60.191.134.206No response
  • 60.191.244.5No response
  • 202.96.104.15No response
— Community list, not officially confirmed
Hebei China Telecom Plain resolution
  • 222.222.202.202No response
— Community list, not officially confirmed
Hainan China Telecom Plain resolution
  • 202.100.192.68No response
— Community list, not officially confirmed
Liaoning China Telecom Plain resolution
  • 219.148.204.66No response
— Community list, not officially confirmed
Jilin China Telecom Plain resolution
  • 219.149.194.55No response
— Community list, not officially confirmed
Xinjiang China Telecom Plain resolution
  • 61.128.114.167No response
— Community list, not officially confirmed
China Unicom · carrier DNS 31 entries · 59 addresses

Carrier DNS addresses by province from community lists, as carriers do not publish a single official list. They usually serve only subscribers on that carrier in the same province; use and test them there.

Name and purpose IPv4 and result IPv6 and result Source
China Unicom IPv6 Plain resolution —
  • 2408:8899::8Not tested
  • 2408:8888::8Not tested
Community list, not officially confirmed
Beijing China Unicom Plain resolution
  • 123.123.123.123Resolves 3/3 rounds · 78 ms
  • 123.123.123.124Resolves 3/3 rounds · 79 ms
  • 202.106.0.20Resolves 2/3 rounds · 1092 ms
  • 202.106.195.68Resolves 2/3 rounds · 2089 ms
— Community list, not officially confirmed
Shanghai China Unicom Plain resolution
  • 210.22.70.3No response
  • 210.22.84.3Refused
  • 210.22.70.225Refused
— Community list, not officially confirmed
Tianjin China Unicom Plain resolution
  • 202.99.104.68No response
  • 202.99.96.68No response
— Community list, not officially confirmed
Chongqing China Unicom Plain resolution
  • 221.5.203.98Refused
  • 221.7.92.98Refused
— Community list, not officially confirmed
Guangdong China Unicom Plain resolution
  • 210.21.196.6Answers, test lookup timed out
  • 221.5.88.88Refused
  • 210.21.4.130Refused
— Community list, not officially confirmed
Hebei China Unicom Plain resolution
  • 202.99.160.68Refused
  • 202.99.166.4Refused
— Community list, not officially confirmed
Henan China Unicom Plain resolution
  • 202.102.224.68No response
  • 202.102.227.68No response
— Community list, not officially confirmed
Heilongjiang China Unicom Plain resolution
  • 202.97.224.69No response
  • 202.97.224.68No response
— Community list, not officially confirmed
Jilin China Unicom Plain resolution
  • 202.98.0.68No response
  • 202.98.5.68No response
— Community list, not officially confirmed
Jiangsu China Unicom Plain resolution
  • 221.6.4.66No response
  • 221.6.4.67No response
  • 58.240.57.33No response
— Community list, not officially confirmed
Inner Mongolia China Unicom Plain resolution
  • 202.99.224.68Refused
  • 202.99.224.8Refused
— Community list, not officially confirmed
Shandong China Unicom Plain resolution
  • 202.102.128.68No response
  • 202.102.152.3No response
  • 202.102.134.68No response
  • 202.102.154.3No response
— Community list, not officially confirmed
Shanxi China Unicom Plain resolution
  • 202.99.192.66No response
  • 202.99.192.68No response
  • 202.97.131.178No response
— Community list, not officially confirmed
Shaanxi China Unicom Plain resolution
  • 221.11.1.67Refused
  • 221.11.1.68Refused
— Community list, not officially confirmed
Sichuan China Unicom Plain resolution
  • 119.6.6.6Refused
  • 124.161.87.155No response
— Community list, not officially confirmed
Zhejiang China Unicom Plain resolution
  • 221.12.1.227No response
  • 221.12.33.227No response
  • 221.12.65.227No response
— Community list, not officially confirmed
Liaoning China Unicom Plain resolution
  • 202.96.69.38Resolves 2/3 rounds · 115 ms
  • 202.96.64.68Resolves 3/3 rounds · 91 ms
— Community list, not officially confirmed
Guizhou China Unicom Plain resolution
  • 221.13.30.242No response
— Community list, not officially confirmed
Gansu China Unicom Plain resolution
  • 221.7.34.11No response
— Community list, not officially confirmed
Ningxia China Unicom Plain resolution
  • 221.199.12.157Refused
— Community list, not officially confirmed
Jiangxi China Unicom Plain resolution
  • 220.248.192.12No response
— Community list, not officially confirmed
Guangxi China Unicom Plain resolution
  • 221.7.128.68No response
— Community list, not officially confirmed
Tibet China Unicom Plain resolution
  • 221.13.65.34No response
— Community list, not officially confirmed
Hainan China Unicom Plain resolution
  • 221.11.132.2Refused
— Community list, not officially confirmed
Hunan China Unicom Plain resolution
  • 58.20.127.238Refused
— Community list, not officially confirmed
Hubei China Unicom Plain resolution
  • 218.104.111.122No response
— Community list, not officially confirmed
Anhui China Unicom Plain resolution
  • 218.104.78.2No response
  • 58.242.2.2No response
— Community list, not officially confirmed
Fujian China Unicom Plain resolution
  • 218.104.128.106No response
— Community list, not officially confirmed
Xinjiang China Unicom Plain resolution
  • 221.7.1.20No response
— Community list, not officially confirmed
Yunnan China Unicom Plain resolution
  • 221.3.131.11No response
— Community list, not officially confirmed
China Mobile · carrier DNS 33 entries · 122 addresses

Carrier DNS addresses by province from community lists, as carriers do not publish a single official list. They usually serve only subscribers on that carrier in the same province; use and test them there.

Name and purpose IPv4 and result IPv6 and result Source
China Mobile IPv6 Plain resolution —
  • 2409:8088::aNot tested
  • 2409:8088::bNot tested
Community list, not officially confirmed
Beijing China Mobile Plain resolution
  • 211.138.30.66No response
  • 211.136.17.107No response
  • 211.136.28.231No response
  • 211.136.28.234No response
  • 211.136.28.237No response
  • 211.136.28.228No response
  • 221.130.32.103No response
  • 221.130.32.100No response
  • 221.130.32.106No response
  • 221.130.32.109No response
  • 221.176.3.70No response
  • 221.176.3.73No response
  • 221.176.3.76No response
  • 221.176.3.79No response
  • 221.176.3.83No response
  • 221.176.3.85No response
  • 221.176.4.6No response
  • 221.176.4.9No response
  • 221.176.4.12No response
  • 221.176.4.15No response
  • 221.176.4.18No response
  • 221.176.4.21No response
  • 221.130.33.52No response
  • 221.179.155.193No response
— Community list, not officially confirmed
Shanghai China Mobile Plain resolution
  • 211.136.112.50No response
  • 211.136.150.66No response
  • 211.136.18.171No response
— Community list, not officially confirmed
Tianjin China Mobile Plain resolution
  • 211.137.160.50No response
  • 211.137.160.185No response
— Community list, not officially confirmed
Chongqing China Mobile Plain resolution
  • 218.201.4.3No response
  • 218.201.21.132No response
  • 218.201.17.2No response
— Community list, not officially confirmed
Anhui China Mobile Plain resolution
  • 211.138.180.2No response
  • 211.138.180.3No response
— Community list, not officially confirmed
Shandong China Mobile Plain resolution
  • 218.201.96.130No response
  • 211.137.191.26No response
  • 218.201.124.18No response
  • 218.201.124.19No response
— Community list, not officially confirmed
Shanxi China Mobile Plain resolution
  • 211.138.106.2No response
  • 211.138.106.3Refused
  • 211.138.106.18No response
  • 211.138.106.19Refused
  • 211.138.106.7No response
— Community list, not officially confirmed
Jiangsu China Mobile Plain resolution
  • 221.131.143.69No response
  • 112.4.0.55No response
  • 221.130.13.133No response
  • 211.103.55.50No response
  • 221.130.56.241No response
  • 211.103.13.101No response
  • 211.138.200.69No response
— Community list, not officially confirmed
Zhejiang China Mobile Plain resolution
  • 211.140.13.188No response
  • 211.140.188.188No response
  • 211.140.10.2No response
— Community list, not officially confirmed
Hunan China Mobile Plain resolution
  • 211.142.210.98No response
  • 211.142.210.99No response
  • 211.142.210.100No response
  • 211.142.210.101No response
  • 211.142.211.124No response
  • 211.142.236.87No response
— Community list, not officially confirmed
Hubei China Mobile Plain resolution
  • 211.137.58.20No response
  • 211.137.64.163No response
— Community list, not officially confirmed
Jiangxi China Mobile Plain resolution
  • 211.141.90.68No response
  • 211.141.90.69Refused
  • 211.141.85.68No response
— Community list, not officially confirmed
Shaanxi China Mobile Plain resolution
  • 211.137.130.3No response
  • 211.137.130.19No response
  • 218.200.6.139No response
— Community list, not officially confirmed
Sichuan China Mobile Plain resolution
  • 211.137.82.4Refused
  • 211.137.96.205No response
— Community list, not officially confirmed
Guangdong China Mobile Plain resolution
  • 211.136.20.203No response
  • 211.136.20.204No response
  • 211.136.192.6No response
  • 211.139.136.68No response
  • 211.139.163.6No response
  • 120.196.165.24No response
— Community list, not officially confirmed
Guangxi China Mobile Plain resolution
  • 211.138.245.180No response
  • 211.136.17.108No response
  • 211.138.240.100No response
— Community list, not officially confirmed
Guizhou China Mobile Plain resolution
  • 211.139.5.29No response
  • 211.139.5.30No response
— Community list, not officially confirmed
Fujian China Mobile Plain resolution
  • 211.138.151.161No response
  • 211.138.156.66No response
  • 218.207.217.241No response
  • 218.207.217.242No response
  • 211.143.181.178No response
  • 211.143.181.179No response
  • 218.207.128.4No response
  • 218.207.130.118No response
  • 211.138.145.194Refused
— Community list, not officially confirmed
Hebei China Mobile Plain resolution
  • 211.143.60.56No response
  • 211.138.13.66No response
  • 111.11.1.1No response
— Community list, not officially confirmed
Henan China Mobile Plain resolution
  • 211.138.24.66No response
— Community list, not officially confirmed
Gansu China Mobile Plain resolution
  • 218.203.160.194No response
  • 218.203.160.195No response
  • 211.139.80.6No response
— Community list, not officially confirmed
Heilongjiang China Mobile Plain resolution
  • 211.137.241.34No response
  • 211.137.241.35No response
  • 218.203.59.216No response
— Community list, not officially confirmed
Jilin China Mobile Plain resolution
  • 211.141.16.99No response
  • 211.141.0.99No response
— Community list, not officially confirmed
Liaoning China Mobile Plain resolution
  • 211.137.32.178No response
  • 211.140.197.58No response
— Community list, not officially confirmed
Yunnan China Mobile Plain resolution
  • 211.139.29.68No response
  • 211.139.29.69No response
  • 211.139.29.150No response
  • 211.139.29.170No response
— Community list, not officially confirmed
Hainan China Mobile Plain resolution
  • 221.176.88.95No response
  • 211.138.164.6No response
— Community list, not officially confirmed
Inner Mongolia China Mobile Plain resolution
  • 211.138.91.1No response
  • 211.138.91.2No response
— Community list, not officially confirmed
Xinjiang China Mobile Plain resolution
  • 218.202.152.130No response
  • 218.202.152.131No response
— Community list, not officially confirmed
Tibet China Mobile Plain resolution
  • 211.139.73.34No response
  • 211.139.73.35No response
  • 211.139.73.50No response
— Community list, not officially confirmed
Qinghai China Mobile Plain resolution
  • 211.138.75.123No response
— Community list, not officially confirmed
Ningxia China Mobile Plain resolution
  • 218.203.123.116No response
— Community list, not officially confirmed
Hong Kong China Mobile Plain resolution
  • 203.142.100.18Refused
  • 203.142.100.21Refused
— Community list, not officially confirmed
China Tietong · carrier DNS 1 entries · 2 addresses

Carrier DNS addresses by province from community lists, as carriers do not publish a single official list. They usually serve only subscribers on that carrier in the same province; use and test them there.

Name and purpose IPv4 and result IPv6 and result Source
Guangdong China Tietong Plain resolution
  • 61.235.70.252No response
  • 211.98.4.1No response
— Community list, not officially confirmed
China Broadnet · carrier DNS 2 entries · 4 addresses

Carrier DNS addresses by province from community lists, as carriers do not publish a single official list. They usually serve only subscribers on that carrier in the same province; use and test them there.

Name and purpose IPv4 and result IPv6 and result Source
Guangdong China Broadnet Plain resolution
  • 103.27.24.1Resolves 3/3 rounds · 41 ms
  • 103.27.24.2No response
— Community list, not officially confirmed
Pearl River Broadband (Guangdong) Plain resolution
  • 116.199.0.200No response
  • 116.116.116.116Refused
— Community list, not officially confirmed
Great Wall Broadband · carrier DNS 1 entries · 2 addresses

Carrier DNS addresses by province from community lists, as carriers do not publish a single official list. They usually serve only subscribers on that carrier in the same province; use and test them there.

Name and purpose IPv4 and result IPv6 and result Source
Guangdong Great Wall Broadband Plain resolution
  • 211.162.78.1No response
  • 211.162.78.2Refused
— Community list, not officially confirmed
Topway · carrier DNS 1 entries · 1 addresses

Carrier DNS addresses by province from community lists, as carriers do not publish a single official list. They usually serve only subscribers on that carrier in the same province; use and test them there.

Name and purpose IPv4 and result IPv6 and result Source
Guangdong Topway Plain resolution
  • 211.148.192.141No response
— Community list, not officially confirmed
Hong Kong, Taiwan and overseas 14 entries · 20 addresses

DNS addresses of regional carriers and organizations, mostly from community lists without official confirmation. Overseas resolvers add latency from mainland China and may return different answers.

Name and purpose IPv4 and result IPv6 and result Source
Chunghwa Telecom HiNet Chunghwa Telecom Plain resolution
  • 168.95.1.1Resolves 3/3 rounds · 155 ms
  • 168.95.192.1Resolves 3/3 rounds · 130 ms
— Community list, not officially confirmed
HKBN (Hong Kong Broadband) HKBN Plain resolution
  • 203.80.96.10No response
  • 203.80.96.9No response
— Community list, not officially confirmed
Hong Kong Plain resolution
  • 103.147.12.3No response
— Community list, not officially confirmed
Hong Kong · Hutchison Plain resolution
  • 210.3.138.237No response
  • 210.0.128.241Answers, test lookup timed out
— Community list, not officially confirmed
Singapore Plain resolution
  • 103.86.99.100Resolves 3/3 rounds · 473 ms
— Community list, not officially confirmed
Singapore Plain resolution
  • 128.106.52.161Resolves 3/3 rounds · 753 ms
  • 116.12.206.109No response
— Community list, not officially confirmed
Japan · Tokyo Plain resolution
  • 211.10.168.1No response
— Community list, not officially confirmed
Japan · Kanagawa Plain resolution
  • 122.210.62.171Resolves 3/3 rounds · 599 ms
— Community list, not officially confirmed
South Korea · Seoul Plain resolution
  • 219.250.36.130Resolves 3/3 rounds · 112 ms
  • 210.220.163.82Resolves 3/3 rounds · 114 ms
— Community list, not officially confirmed
South Korea · Seoul Plain resolution
  • 203.248.252.2Resolves 3/3 rounds · 353 ms
— Community list, not officially confirmed
South Korea · KT Plain resolution
  • 168.126.63.1Resolves 3/3 rounds · 254 ms
— Community list, not officially confirmed
Malaysia · Kuala Lumpur Plain resolution
  • 163.47.202.150Resolves 3/3 rounds · 429 ms
  • 175.138.229.245No response
— Community list, not officially confirmed
Philippines · Manila Plain resolution
  • 124.105.217.62Resolves 3/3 rounds · 723 ms
— Community list, not officially confirmed
Vietnam · Long An Plain resolution
  • 113.161.228.6No response
— Community list, not officially confirmed
Cloud-internal DNS 2 entries · 9 addresses

Resolvers that cloud providers offer to their own servers, not public DNS for home broadband.

Name and purpose IPv4 and result IPv6 and result Source
Tencent Cloud Private DNS default servers Tencent Cloud Plain resolution Intended for servers inside Tencent Cloud VPCs, not a public resolver for home broadband.
  • 183.60.83.19No response
  • 183.60.82.98No response
— Official source checked (2026-11-07) cloud.tencent.com/document/product/1338/106568
Huawei Cloud addresses (from the reference list) Huawei Cloud Plain resolution No Huawei Cloud documentation publishes these as public resolvers. Its intranet DNS is assigned per region; check the cloud console.
  • 122.112.208.1Resolves 3/3 rounds · 72 ms
  • 139.9.23.90Resolves 3/3 rounds · 58 ms
  • 114.115.192.11Resolves 3/3 rounds · 133 ms
  • 116.205.5.1Resolves 3/3 rounds · 150 ms
  • 116.205.5.30Resolves 3/3 rounds · 140 ms
  • 122.112.208.175Resolves 3/3 rounds · 70 ms
  • 139.159.208.206Resolves 3/3 rounds · 66 ms
— Community list, not officially confirmed
Retired or unconfirmed old addresses 7 entries · 10 addresses

Addresses whose service was officially retired, that no longer appear in official documentation, or that were mislabeled on the reference site. Kept for lookup; not recommended for use.

Name and purpose IPv4 and result IPv6 and result Source
Norton ConnectSafe (retired) Norton Plain resolution Norton states that ConnectSafe was retired on November 15, 2018.
  • 199.85.126.10No response
  • 199.85.127.10No response
— Not recommended support.norton.com/sp/en/in/norton-utilities/16.0/solutions/v53246991
DNS.SB former address DNS.SB Plain resolution DNS.SB now lists 45.11.45.11 as its second address; this one is no longer listed.
  • 185.184.222.222No response
— Not recommended
DNSPod former address Tencent Cloud Plain resolution Current Tencent Public DNS documentation lists only 119.29.29.29 for IPv4.
  • 182.254.116.116No response
— Not recommended
OneDNS former address ThreatBook Plain resolution Not among the currently listed OneDNS addresses.
  • 117.50.11.11No response
— Not recommended
Baidu Public DNS IPv6 (from the reference list) Baidu Plain resolution Baidu currently lists only the IPv4 address 180.76.76.76. —
  • 2400:da00::6666Not tested
Not recommended
V2EX DNS Plain resolution No current official documentation was found.
  • 199.91.73.222No response
  • 178.79.131.110No response
— Not recommended
Level 3 (Lumen) resolvers Lumen Plain resolution Mislabeled on the reference site as Microsoft Cloud. These belong to Level 3 (now Lumen) and are not an officially public service.
  • 4.2.2.1Resolves 3/3 rounds · 345 ms
  • 4.2.2.2Resolves 3/3 rounds · 364 ms
— Not recommended

Test on your own network

Browsers cannot send raw DNS queries, so run these commands in a terminal, replacing 223.5.5.5 with the address to test:

dig @223.5.5.5 www.baidu.com A
dig +tcp @223.5.5.5 www.baidu.com A
dig @223.5.5.5 test-random.invalid A
nslookup www.baidu.com 223.5.5.5
  • The first command uses UDP and the second TCP; “status: NOERROR” with ANSWER records means the server resolves.
  • The third command queries a nonexistent name and should show “status: NXDOMAIN”; an IP answer means redirection.
  • Ping alone is unreliable: many DNS servers ignore ping, and answering ping does not mean resolving.

Example

Input

Search for 223.5.5.5

Example result

AliDNS · plain resolution · official source checked · 223.5.5.5 resolves from the test node

You can also search by province (e.g. Fujian), carrier (e.g. Unicom) or provider name; tick the option to show only addresses that resolved from the test node.

Technical details & limits

Testing uses script/dns_probe.php, which sends two real DNS queries to every address: an A query for www.baidu.com and a random name under the RFC 6761 reserved .invalid TLD, which must return NXDOMAIN; an IP answer means nonexistent-domain redirection. Timeout is 4 seconds with 1 retry. Before testing, the script queries RFC 5737 documentation addresses and aborts if any answer, since that means local DNS interception. Results only reflect the test node’s network and time; carrier DNS usually serves its own subscribers, so no response from elsewhere does not mean failure.

About this tool

A directory of public recursive resolvers, filtering resolvers, provincial DNS for China Telecom, Unicom, Mobile and other carriers, regional resolvers in Hong Kong, Taiwan and abroad, cloud-internal DNS, and retired or unconfirmed old addresses. Each entry states its source (official page with check date, third-party directory or community list) and purpose (plain, security, family or ad filtering), and every address shows live results from this site’s test node. Search by name, province, carrier or IP and copy addresses with one click.

How to use

  1. Read the test node, protocol and time at the top to understand what the results cover.
  2. Search by name, province, carrier or IP, or filter by group; carrier groups are collapsed by default.
  3. Copy an address and test it on your own network with the dig/nslookup commands at the bottom.

Input & output

Input
Name, province, carrier or IP keywords (up to 40 characters).
Output
DNS addresses (IPv4/IPv6), DoH/DoT endpoints, purpose, source and test-node results.
Limits
Your browser does not send DNS queries here; results come from this site’s test node and do not represent your network. Authoritative NS records are not covered.

Notes

Changing DNS can affect speed and reachability. Filtering resolvers block some sites; use carrier DNS only on that carrier’s network in the matching province.

FAQ

How should I choose between 114DNS, AliDNS and Tencent DNS?
No resolver is best for every network. 223.5.5.5, 119.29.29.29 and 114.114.114.114 have all been checked against their official pages. Use two different providers for primary and secondary DNS, and run dig against each about 3 times from your own connection to compare response times, because results depend heavily on your carrier, province and current routing conditions. Avoid filtering resolvers when you only need plain lookups.
Why do many carrier DNS servers show no response?
Carrier DNS servers usually serve port 53 only to their own subscribers in that province, so queries from other networks often time out or return REFUSED, which is RCODE 5. That does not mean the server has stopped working. To judge a carrier DNS server fairly, test it from a broadband or mobile connection on that carrier in the matching province.
How can I tell whether a DNS server redirects or hijacks lookups?
Query a name that cannot exist, such as a random label under .invalid. RFC 6761 reserves that top-level domain, so an honest resolver must answer NXDOMAIN, which is RCODE 3. If the server returns an IP address instead, it redirects nonexistent names somewhere else, often to a search or advertising page, and this page marks such addresses in the results.

Related tools

Public DNS server list · Public resolvers and Chinese carrier DNS by province, with official sources, purpose and live test results
Public DNS server list — Tool illustration · dayeku.com