DNSWHOIS.INFO - 50.125.122.in-addr.arpa
Search for IP or hostnames:
50.125.122.in-addr.arpa checked at 2025-10-25T00:11:26.452Z 433ms 44/44/44 100% R:1350.125.122.in-addr.arpa
| NS | ipdns1.hinet.net | ||||||
| A | 2001:b000:168::1:400:1 🇹🇼 HiNet | ||||||
| PTR | ipdns1.hinet.net | ||||||
| A | 168.95.192.14🇹🇼 HiNet | ||||||
| PTR | ipdns1.hinet.net | ||||||
| NS | ipdns2.hinet.net | ||||||
| A | 2001:b000:180:80d:203:74:116:214 🇹🇼 HiNet | ||||||
| PTR | ipdns2.hinet.net | ||||||
| A | 203.74.116.214🇹🇼 HiNet | ||||||
| PTR | ipdns2.hinet.net | ||||||
125.122.in-addr.arpa
| NS | ipdnsb1.hinet.net | ||||||
| NS | ipdnsb2.hinet.net | ||||||
Up
204.50.125.122.in-addr.arpa |
155.50.125.122.in-addr.arpa |
183.50.125.122.in-addr.arpa |
111.50.125.122.in-addr.arpa |
3.50.125.122.in-addr.arpa |
141.50.125.122.in-addr.arpa |
93.50.125.122.in-addr.arpa |
94.50.125.122.in-addr.arpa |
101.50.125.122.in-addr.arpa |
168.50.125.122.in-addr.arpa |
133.50.125.122.in-addr.arpa |
179.50.125.122.in-addr.arpa |
12.50.125.122.in-addr.arpa |
197.50.125.122.in-addr.arpa |
113.50.125.122.in-addr.arpa |
38.50.125.122.in-addr.arpa |
56.50.125.122.in-addr.arpa |
22.50.125.122.in-addr.arpa |
153.50.125.122.in-addr.arpa |
242.50.125.122.in-addr.arpa |
8.50.125.122.in-addr.arpa |
Starts with same word
Starts similarily
AI analysis
50.125.122.in-addr.arpa is a parent of 204.50.125.122.in-addr.arpa, 155.50.125.122.in-addr.arpa, 183.50.125.122.in-addr.arpa, 111.50.125.122.in-addr.arpa, 3.50.125.122.in-addr.arpa and a few other host names.
Two name servers ipdns1.hinet.net and ipdns2.hinet.net handle the delegation for 50.125.122.in-addr.arpa.
50.125.122.in-addr.arpa shares the same name server setup as other domains, for example 185.112.59.in-addr.arpa, 149.127.122.in-addr.arpa, 47.161.118.in-addr.arpa, 151.37.114.in-addr.arpa and 22.230.125.in-addr.arpa.
Host names with two IP numbers:
ipdns1.hinet.net points to 2001:b000:168::1:400:1 and 168.95.192.14.
ipdns2.hinet.net points to 2001:b000:180:80d:203:74:116:214 and 203.74.116.214.