DNSWHOIS.INFO - 192.245.216.in-addr.arpa
Search for IP or hostnames:
192.245.216.in-addr.arpa checked at 2025-10-07T05:49:28.153Z 110ms 50/50/50 100% R:9
192.245.216.in-addr.arpa
NS | ns1.limestonenetworks.com | ||||||
A | 2607:ff68:5::300 🇺🇸 Limestone Networks | ||||||
PTR | ns1.dallas-idc.com | ||||||
A | 64.31.5.3🇺🇸 Limestone Networks | ||||||
PTR | ns1.dallas-idc.com | ||||||
NS | ns2.limestonenetworks.com | ||||||
A | 2607:ff68:5::400 🇺🇸 Limestone Networks | ||||||
A | 64.31.5.4🇺🇸 Limestone Networks | ||||||
PTR | ns2.dallas-idc.com |
245.216.in-addr.arpa
Up
214.192.245.216.in-addr.arpa |
70.192.245.216.in-addr.arpa |
218.192.245.216.in-addr.arpa |
105.192.245.216.in-addr.arpa |
178.192.245.216.in-addr.arpa |
187.192.245.216.in-addr.arpa |
28.192.245.216.in-addr.arpa |
164.192.245.216.in-addr.arpa |
21.192.245.216.in-addr.arpa |
19.192.245.216.in-addr.arpa |
134.192.245.216.in-addr.arpa |
59.192.245.216.in-addr.arpa |
54.192.245.216.in-addr.arpa |
99.192.245.216.in-addr.arpa |
20.192.245.216.in-addr.arpa |
18.192.245.216.in-addr.arpa |
30.192.245.216.in-addr.arpa |
Starts with same word
Starts similarily
AI analysis
192.245.216.in-addr.arpa
is a parent of 214.192.245.216.in-addr.arpa
, 70.192.245.216.in-addr.arpa
, 218.192.245.216.in-addr.arpa
, 105.192.245.216.in-addr.arpa
, 178.192.245.216.in-addr.arpa
and a few other host names.
192.245.216.in-addr.arpa
's delegation uses two name servers, ns1.limestonenetworks.com
and ns2.limestonenetworks.com
.
192.245.216.in-addr.arpa
shares the same name server setup as other domains, for example 219.245.216.in-addr.arpa
, 206.115.208.in-addr.arpa
, 101.162.69.in-addr.arpa
, 103.162.69.in-addr.arpa
and promoteammexico.com
.
192.245.216.in-addr.arpa
partially shares its name servers with other domains, for example lstn.net
and gerentenet.com
.
these name servers are commonly used together with ns3.limestonenetworks.com
, ns1.dallas-idc.com
and ns2.dallas-idc.com
.
Host names with two IPs:
ns1.limestonenetworks.com
points to: 2607:ff68:5::300 and 64.31.5.3
ns2.limestonenetworks.com
points to: 2607:ff68:5::400 and 64.31.5.4