Öffentliche Nameserver
Tipps: Kostenloser DynDNS-Dienst mit IPv6 | TLS Check
DNS-Server aus Nepal
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 |
|---|---|---|---|---|---|---|
| 118.91.170.243 | Sorry not available |
gültig
|
93 % | Whois | ||
| 110.44.112.102 | Kathmandu | dnsmasq-2.45 |
gültig
|
100 % | Whois | |
| 116.90.234.126 |
gültig
|
72 % | Whois | |||
| 110.44.123.15 | Kathmandu | Intentionally left blank! |
gültig
|
90 % | Whois | |
| 202.51.76.130 | Kathmandu | Intentionally left blank! |
gültig
|
97 % | Whois | |
| 110.44.121.147 | Kathmandu |
gültig
|
97 % | Whois | ||
| 110.44.122.200 | Kathmandu |
gültig
|
97 % | Whois | ||
| 103.232.155.243 | 9.6.1-P3 |
gültig
|
59 % | Whois | ||
| 110.34.24.200 | Kathmandu |
gültig
|
97 % | Whois | ||
| 110.34.27.169 | Kathmandu | 9.6.1-P3 |
gültig
|
59 % | Whois | |
| 110.34.24.204 | Kathmandu |
gültig
|
97 % | Whois | ||
| 110.34.24.26 | Kathmandu | Microsoft DNS 6.1.7601 (1DB1446A) |
gültig
|
97 % | Whois | |
| 110.34.27.48 | Kathmandu | 9.6.1-P3 |
gültig
|
69 % | Whois | |
| 110.34.24.132 | Kathmandu |
gültig
|
97 % | Whois | ||
|
202.63.241.168
mail.rss.com.np.
|
Kathmandu | 9.3.1 |
gültig
|
93 % | Whois | |
| 182.93.82.4 | Kathmandu | dnsmasq-2.40 |
gültig
|
86 % | Whois | |
|
103.255.126.3
ns2.f1soft.com.np.126.255.103.in-addr.arpa.
|
PowerDNS Authoritative Server 3.4.8 (jenkins@autotest.powerdns.com built 20160618153635 mockbuild@buildvm-19.phx2.fedoraproject.org) |
gültig
|
97 % | Whois | ||
| 202.50.53.2 | Kathmandu | Microsoft DNS 6.1.7601 (1DB15D39) |
gültig
|
97 % | Whois | |
|
103.233.58.25
c3-vps-25.accessworld.net.
|
gültig
|
97 % | Whois | |||
|
202.79.51.55
55.51.79.202.ether.static.wlink.com.np.
|
gültig
|
93 % | Whois | |||
| 103.207.81.6 |
gültig
|
97 % | Whois | |||
| 202.51.74.33 | Kathmandu |
gültig
|
97 % | Whois | ||
|
202.45.144.212
144-212.nitc.gov.np.
|
gültig
|
100 % | Whois | |||
| 103.254.184.115 | Tansen |
gültig
|
90 % | Whois | ||
| 103.58.145.63 | Bhojpur |
gültig
|
97 % | Whois | ||
| 202.51.74.97 | Kathmandu |
gültig
|
97 % | Whois | ||
| 202.51.74.187 | Kathmandu |
gültig
|
97 % | Whois | ||
| 115.187.17.50 | 9.2.4 |
gültig
|
100 % | Whois | ||
| 116.90.234.218 |
i/o timeout
|
69 % | Whois | |||
| 110.44.122.22 | Kathmandu |
i/o timeout
|
90 % | Whois | ||
| 110.44.115.122 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 110.44.115.125 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 110.44.121.201 | Kathmandu |
i/o timeout
|
45 % | Whois | ||
| 110.44.121.212 | Kathmandu |
i/o timeout
|
34 % | Whois | ||
| 110.44.113.234 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 103.10.31.5 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 103.10.31.7 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 43.245.87.91 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 116.90.234.102 |
i/o timeout
|
0 % | Whois | |||
| 116.90.234.114 |
i/o timeout
|
0 % | Whois | |||
| 43.245.87.168 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 116.90.234.186 |
i/o timeout
|
0 % | Whois | |||
| 43.245.87.213 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 43.245.87.234 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 103.232.155.251 |
i/o timeout
|
52 % | Whois | |||
| 103.232.155.102 |
i/o timeout
|
0 % | Whois | |||
| 103.232.152.146 |
i/o timeout
|
0 % | Whois | |||
| 103.232.153.160 |
i/o timeout
|
0 % | Whois | |||
| 103.232.155.188 |
i/o timeout
|
45 % | Whois | |||
| 103.232.155.228 |
i/o timeout
|
0 % | Whois | |||
| 103.232.155.229 |
i/o timeout
|
0 % | Whois | |||
| 103.235.196.184 |
i/o timeout
|
0 % | Whois | |||
| 103.235.197.195 |
i/o timeout
|
0 % | Whois | |||
| 110.34.12.8 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 110.34.12.14 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 110.34.12.140 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 103.235.196.143 |
i/o timeout
|
0 % | Whois | |||
| 103.235.196.158 |
i/o timeout
|
0 % | Whois | |||
| 103.235.196.161 |
i/o timeout
|
0 % | Whois | |||
| 110.34.15.200 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 110.34.27.205 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 110.34.27.90 | Kathmandu |
i/o timeout
|
10 % | Whois | ||
| 110.34.27.117 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 110.34.27.7 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 110.34.27.17 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 110.34.27.27 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 110.34.27.40 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 110.34.27.57 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 103.232.155.139 | 9.6.1-P3 |
SERVFAIL for verisignlabs.com
|
52 % | Whois | ||
| 110.34.27.4 | Kathmandu |
i/o timeout
|
52 % | Whois | ||
| 202.51.91.252 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 116.90.234.93 |
connection refused
|
0 % | Whois | |||
| 202.51.90.131 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 116.66.199.159 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 116.66.199.164 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 202.51.90.157 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
|
110.34.26.194
mail.sbl.com.np.
|
Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 116.66.198.218 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 116.66.196.7 | Kathmandu |
i/o timeout
|
45 % | Whois | ||
| 116.66.196.112 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 116.66.197.183 | Kathmandu |
i/o timeout
|
55 % | Whois | ||
| 116.66.197.190 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 163.47.151.249 |
i/o timeout
|
0 % | Whois | |||
| 163.47.148.15 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 163.47.148.16 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 163.47.148.31 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 163.47.148.39 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 202.51.90.42 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 103.232.155.106 | 9.6.1-P3 |
SERVFAIL for verisignlabs.com
|
69 % | Whois | ||
| 202.51.90.138 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 202.51.90.146 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 182.93.81.168 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 163.47.148.8 | Kathmandu |
i/o timeout
|
59 % | Whois | ||
| 202.51.90.84 | Kathmandu |
i/o timeout
|
3 % | Whois | ||
| 202.50.55.174 | Kathmandu |
i/o timeout
|
0 % | Whois | ||
| 116.90.234.163 |
connection refused
|
0 % | Whois | |||
| 202.50.55.229 | Kathmandu |
i/o timeout
|
28 % | Whois | ||
| 103.235.197.198 | 9.6.1-P3 |
SERVFAIL for verisignlabs.com
|
55 % | Whois | ||
| 103.235.197.209 | 9.6.1-P3 |
SERVFAIL for verisignlabs.com
|
62 % | Whois | ||
|
139.5.71.71
71.71.5.139.static.wlink.com.np.
|
i/o timeout
|
10 % | Whois |
View this page in english | Änderungen | Impressum | bithopper (at) jabber.ccc.de [OTR Fingerprint: 2748EB64 5E884014 9CD6D73E 50AEBA8E 559AC8C7] | Powered by Ruby On Rails | Leckere Cocktails gefällig?