Öffentliche Nameserver
Tipps: Kostenloser DynDNS-Dienst mit IPv6 | TLS Check
DNS-Server aus China
Die hier gelisteten Nameserver werden ständig auf Erreichbarkeit und Funktionalität getestet . Eine Anleitung vom CCC (für verschiedene Betriebssysteme) und ein Video von Youtube (für Windows) helfen bei der Einrichtung von alternativen Nameservern.
| IPv4/IPv6 Adresse | Standort | Software / Version | zuletzt überprüft | Status | Reliability | Whois |
|---|---|---|---|---|---|---|
|
202.46.42.130
ptr.cnsat.com.cn.
|
Shenzhen |
gültig
|
100 % | Whois | ||
|
202.46.37.21
ptr.cnsat.com.cn.
|
Shenzhen |
gültig
|
100 % | Whois | ||
|
202.46.37.20
ptr.cnsat.com.cn.
|
Shenzhen |
gültig
|
100 % | Whois | ||
|
202.46.36.130
ptr.cnsat.com.cn.
|
Shenzhen |
gültig
|
95 % | Whois | ||
|
202.46.36.128
ptr.cnsat.com.cn.
|
Shenzhen |
gültig
|
95 % | Whois | ||
|
202.46.36.129
ptr.cnsat.com.cn.
|
Shenzhen |
gültig
|
95 % | Whois | ||
|
202.46.36.131
ptr.cnsat.com.cn.
|
Shenzhen |
gültig
|
95 % | Whois | ||
|
202.46.36.132
ptr.cnsat.com.cn.
|
Shenzhen |
gültig
|
95 % | Whois | ||
|
202.46.36.133
ptr.cnsat.com.cn.
|
Shenzhen |
gültig
|
28 % | Whois | ||
|
202.46.36.3
ptr.cnsat.com.cn.
|
Shenzhen |
gültig
|
100 % | Whois | ||
|
202.46.34.75
svr75.efeedlink.com.
|
Shenzhen | 9.9.4-RedHat-9.9.4-61.el7 |
gültig
|
100 % | Whois | |
|
202.46.34.76
svr76.efeedlink.com.
|
Shenzhen | 9.9.4-RedHat-9.9.4-61.el7 |
gültig
|
98 % | Whois | |
|
202.46.34.74
svr74.efeedlink.com.
|
Shenzhen | 9.9.4-RedHat-9.9.4-61.el7 |
gültig
|
100 % | Whois | |
|
202.46.32.22
ptr.cnsat.com.cn.
|
Shenzhen |
gültig
|
100 % | Whois | ||
|
202.46.32.19
ns1.cnsat.com.cn.
|
Shenzhen |
gültig
|
100 % | Whois | ||
|
202.46.32.187
ptr.cnsat.com.cn.
|
Shenzhen | 9.6-ESV-R5-P1 |
gültig
|
98 % | Whois | |
|
114.114.114.110
protect-children-1.114dns.com.
|
Nanjing |
gültig
|
100 % | Whois | ||
|
114.114.115.110
protect-children-2.114dns.com.
|
Nanjing |
gültig
|
100 % | Whois | ||
| 198.15.67.245 | Microsoft DNS 6.0.6002 (17724D35) |
gültig
|
100 % | Whois | ||
|
114.114.115.119
anti-malware-2.114dns.com.
|
Nanjing |
gültig
|
100 % | Whois | ||
|
180.76.76.76
public-dns-a.baidu.com.
|
Beijing | baidu dns |
gültig
|
100 % | Whois | |
|
114.114.114.119
anti-malware-1.114dns.com.
|
Nanjing |
gültig
|
100 % | Whois | ||
|
114.114.115.115
public2.114dns.com.
|
Nanjing |
gültig
|
100 % | Whois | ||
| 210.2.4.8 | Beijing |
gültig
|
80 % | Whois | ||
|
114.114.114.114
public1.114dns.com.
|
Nanjing |
gültig
|
100 % | Whois | ||
| 240c::6666 |
gültig
|
98 % | Whois | |||
| 240c::6644 |
gültig
|
98 % | Whois | |||
| 103.75.236.250 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.251 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.252 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.253 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.254 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.255 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.241 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.242 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.243 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.244 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.245 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.246 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.247 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.248 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.249 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.230 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.231 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.232 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.233 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.234 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.235 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.236 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.237 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.238 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.239 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.240 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.221 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.222 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.223 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.224 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.225 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.226 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.227 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.228 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.229 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.208 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.209 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.210 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.211 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.212 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.213 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.214 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.215 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.216 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.217 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.218 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.219 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.220 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.197 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.198 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.199 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.200 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.201 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.202 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.203 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.204 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.205 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.206 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.207 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.190 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.191 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.192 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.193 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.194 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.195 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.196 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.184 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.185 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.186 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.187 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.188 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.189 | Jiading |
i/o timeout
|
0 % | Whois | ||
| 103.75.236.172 | Jiading |
i/o timeout
|
0 % | Whois |
View this page in english | Änderungen | Impressum | Datenschutz | bithopper (at) jabber.ccc.de [OTR Fingerprint: 2748EB64 5E884014 9CD6D73E 50AEBA8E 559AC8C7] | Powered by Ruby On Rails | Leckere Cocktails gefällig?