Searching for 99.63.154.198.in-addr.arpa. PTR record at D.ROOT-SERVERS.NET. [199.7.91.13]
...took 12 ms
Searching for 99.63.154.198.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 251 ms
REFUSED
Searching for 99.63.154.198.in-addr.arpa. PTR record at ns2.fortacloud.co. [108.59.12.101] ...took 93 ms
REFUSED
Searching for 99.63.154.198.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 251 ms
Searching for z.arin.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for z.arin.net. A record at m.gtld-servers.net. [192.55.83.30] ...took 11 ms
Searching for z.arin.net. A record at u.arin.net. [204.61.216.50] ...took 11 ms
Searching for 99.63.154.198.in-addr.arpa. PTR record at z.arin.net. [199.180.180.63]
...took 152 msSearching for z.arin.net. A record at m.gtld-servers.net. [192.55.83.30] ...took 11 ms
Searching for z.arin.net. A record at u.arin.net. [204.61.216.50] ...took 11 ms
Searching for ns2.fortacloud.co. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 13 ms
Searching for ns2.fortacloud.co. A record at ns3.cctld.co. [37.209.196.14] ...took 5 ms
Searching for 99.63.154.198.in-addr.arpa. PTR record at ns2.fortacloud.co. [108.59.12.101]
...took 96 msSearching for ns2.fortacloud.co. A record at ns3.cctld.co. [37.209.196.14] ...took 5 ms
Searching for ns1.milesmx.com. A record at B.ROOT-SERVERS.NET. [192.228.79.201]
...took 19 ms
Searching for ns1.milesmx.com. A record at e.gtld-servers.net. [192.12.94.30] ...took 23 ms
Searching for ns1.milesmx.com. A record at ns-uk.topdns.com. [77.247.183.137] ...took 11 ms
Searching for ns2.fortacloud.co. A record at ns1.milesmx.com. [108.59.12.92]
...took 95 msSearching for ns1.milesmx.com. A record at e.gtld-servers.net. [192.12.94.30] ...took 23 ms
Searching for ns1.milesmx.com. A record at ns-uk.topdns.com. [77.247.183.137] ...took 11 ms
REFUSED
Searching for 99.63.154.198.in-addr.arpa. PTR record at ns2.fortacloud.co. [108.59.12.101] ...took 93 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 806 ms