Searching for 132.100.163.152.in-addr.arpa. PTR record at D.ROOT-SERVERS.NET. [199.7.91.13]
...took 12 ms
Searching for 132.100.163.152.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
REFUSED
Searching for 132.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 132.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 121 ms
REFUSED
Searching for 132.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 132.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 148 ms
REFUSED
Searching for 132.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 120 ms
REFUSED
Searching for 132.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 10 ms
REFUSED
Searching for 132.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 148 ms
REFUSED
Searching for 132.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 132.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 261 ms
REFUSED
Searching for 132.100.163.152.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
Searching for x.arin.net. A record at D.ROOT-SERVERS.NET. [199.7.91.13]
...took 11 ms
Searching for x.arin.net. A record at d.gtld-servers.net. [192.31.80.30] ...took 23 ms
Searching for x.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 88 ms
Searching for 132.100.163.152.in-addr.arpa. PTR record at x.arin.net. [199.180.180.63]
...took 153 msSearching for x.arin.net. A record at d.gtld-servers.net. [192.31.80.30] ...took 23 ms
Searching for x.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 88 ms
Searching for ns5.yahoo.com. A record at D.ROOT-SERVERS.NET. [199.7.91.13]
...took 11 ms
Searching for ns5.yahoo.com. A record at h.gtld-servers.net. [192.54.112.30] ...took 6 ms
Searching for ns5.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 149 ms
Searching for 132.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53]
...took 255 msSearching for ns5.yahoo.com. A record at h.gtld-servers.net. [192.54.112.30] ...took 6 ms
Searching for ns5.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 149 ms
REFUSED
Searching for 132.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 132.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 121 ms
REFUSED
Searching for 132.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 132.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 148 ms
REFUSED
Searching for 132.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 120 ms
REFUSED
Searching for 132.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 10 ms
REFUSED
Searching for 132.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 148 ms
REFUSED
Searching for 132.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 132.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 261 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,548 ms