Searching for 137.100.163.152.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for 137.100.163.152.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 184 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 172 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 150 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 150 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 177 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 123 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 9 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 184 ms
Searching for r.arin.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for r.arin.net. A record at f.gtld-servers.net. [192.35.51.30] ...took 7 ms
Searching for r.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 94 ms
Searching for 137.100.163.152.in-addr.arpa. PTR record at r.arin.net. [199.180.180.63]
...took 91 msSearching for r.arin.net. A record at f.gtld-servers.net. [192.35.51.30] ...took 7 ms
Searching for r.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 94 ms
Searching for ns4.yahoo.com. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns4.yahoo.com. A record at k.gtld-servers.net. [192.52.178.30] ...took 12 ms
Searching for ns4.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157]
...took 126 msSearching for ns4.yahoo.com. A record at k.gtld-servers.net. [192.52.178.30] ...took 12 ms
Searching for ns4.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 172 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 150 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 150 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 177 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 123 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 9 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,377 ms