NSLIST.NET - 164.62.50.in-addr.arpa
Search for IP or hostnames:
164.62.50.in-addr.arpa checked at 2025-11-19T10:34:13.764Z 289ms 50/50/50 100% R:9 allDone:true timedOut:false 164.62.50.in-addr.arpa
| NS | cns1.secureserver.net | ||||||
| A | 2603:5:2100::64 🇺🇸 GODADDY-DNS-GLOBAL | ||||||
| PTR | cns1.godaddy.com | ||||||
| A | 97.74.96.100🇺🇸 GODADDY-DNS-GLOBAL | ||||||
| PTR | cns1.godaddy.com | ||||||
| NS | cns2.secureserver.net | ||||||
| A | 2603:5:2200::64 🇺🇸 GODADDY-DNS-GLOBAL | ||||||
| PTR | cns2.godaddy.com | ||||||
| A | 173.201.64.100🇺🇸 GODADDY-DNS-GLOBAL | ||||||
| PTR | cns2.godaddy.com | ||||||
62.50.in-addr.arpa
| NS | cns1.secureserver.net | ||||||
| NS | cns2.secureserver.net | ||||||
Up
166.164.62.50.in-addr.arpa |
201.164.62.50.in-addr.arpa |
206.164.62.50.in-addr.arpa |
240.164.62.50.in-addr.arpa |
25.164.62.50.in-addr.arpa |
49.164.62.50.in-addr.arpa |
Starts with same word
164.in |
164.biz |
164.co.uk |
164.com |
164.se |
164.de |
164.in-addr.arpa |
164.net |
164.pl |
164.tv |
164.us |
164.org |
164.ch |
164.su |
164.co |
164.digital |
164.eu |
164.fr |
164.ru |
164.cc |
164.cn |
164.io |
164.ph |
164.at |
164.nl |
164.info |
164.ca |
164.cz |
164.jp |
Starts similarily
AI analysis
164.62.50.in-addr.arpa is a parent of 166.164.62.50.in-addr.arpa, 201.164.62.50.in-addr.arpa, 206.164.62.50.in-addr.arpa, 240.164.62.50.in-addr.arpa, 25.164.62.50.in-addr.arpa and several other host names.
164.62.50.in-addr.arpa is delegated to two name servers: cns1.secureserver.net and cns2.secureserver.net.
164.62.50.in-addr.arpa shares the same name server setup as other domains, for example 42.168.184.in-addr.arpa, 74.97.in-addr.arpa, 124.168.184.in-addr.arpa, 93.238.104.in-addr.arpa and 177.202.64.in-addr.arpa.
164.62.50.in-addr.arpa at least partially shares its name servers with other domains, for instance agrosilos.cl.
These name servers are often used with ns05.domaincontrol.com and ns06.domaincontrol.com.
Host names with two IP numbers:
cns1.secureserver.net points to 2603:5:2100::64 and 97.74.96.100
cns2.secureserver.net points to 2603:5:2200::64 and 173.201.64.100