IPLIST.NET - 173.62.50.in-addr.arpa
Search for IP or hostnames:
173.62.50.in-addr.arpa checked at 2025-10-24T12:55:23.105Z 974ms 44/44/44 100% R:9173.62.50.in-addr.arpa
| NS | cns1.secureserver.net | ||||||
| A | 2603:5:2100::64 🇺🇸 GODADDY-DNS | ||||||
| PTR | cns1.godaddy.com | ||||||
| A | 97.74.96.100🇺🇸 GODADDY-DNS | ||||||
| PTR | cns1.godaddy.com | ||||||
| NS | cns2.secureserver.net | ||||||
| A | 2603:5:2200::64 🇺🇸 GODADDY-DNS | ||||||
| PTR | cns2.godaddy.com | ||||||
| A | 173.201.64.100🇺🇸 GODADDY-DNS | ||||||
| PTR | cns2.godaddy.com | ||||||
62.50.in-addr.arpa
| NS | cns1.secureserver.net | ||||||
| NS | cns2.secureserver.net | ||||||
Up
60.173.62.50.in-addr.arpa |
147.173.62.50.in-addr.arpa |
26.173.62.50.in-addr.arpa |
162.173.62.50.in-addr.arpa |
126.173.62.50.in-addr.arpa |
18.173.62.50.in-addr.arpa |
129.173.62.50.in-addr.arpa |
58.173.62.50.in-addr.arpa |
86.173.62.50.in-addr.arpa |
165.173.62.50.in-addr.arpa |
237.173.62.50.in-addr.arpa |
247.173.62.50.in-addr.arpa |
53.173.62.50.in-addr.arpa |
175.173.62.50.in-addr.arpa |
118.173.62.50.in-addr.arpa |
208.173.62.50.in-addr.arpa |
69.173.62.50.in-addr.arpa |
231.173.62.50.in-addr.arpa |
181.173.62.50.in-addr.arpa |
178.173.62.50.in-addr.arpa |
138.173.62.50.in-addr.arpa |
Starts with same word
Starts similarily
AI analysis
173.62.50.in-addr.arpa is the parent of 60.173.62.50.in-addr.arpa, 147.173.62.50.in-addr.arpa, 26.173.62.50.in-addr.arpa, 162.173.62.50.in-addr.arpa, 126.173.62.50.in-addr.arpa and a few other host names.
Two name servers cns1.secureserver.net and cns2.secureserver.net are delegated to 173.62.50.in-addr.arpa.
173.62.50.in-addr.arpa uses the same name server configuration as other domains, such as 81.72.148.in-addr.arpa, godaddy.eg, 82.62.50.in-addr.arpa, 233.178.68.in-addr.arpa and 217.168.184.in-addr.arpa.
Host names with two IPs:
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.
dbq