Searching for 137.100.163.152.in-addr.arpa. PTR record at I.ROOT-SERVERS.NET. [192.36.148.17]
...took 12 ms
Searching for 137.100.163.152.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 15 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 5 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 143 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 127 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 125 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 10 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 142 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 267 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 b.in-addr-servers.arpa. [199.253.183.183] ...took 15 ms
Searching for arin.authdns.ripe.net. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 11 ms
Searching for arin.authdns.ripe.net. A record at i.gtld-servers.net. [192.43.172.30] ...took 6 ms
Searching for arin.authdns.ripe.net. A record at rirns.arin.net. [199.253.249.53] ...took 155 ms
Searching for 137.100.163.152.in-addr.arpa. PTR record at arin.authdns.ripe.net. [193.0.9.10]
...took 12 msSearching for arin.authdns.ripe.net. A record at i.gtld-servers.net. [192.43.172.30] ...took 6 ms
Searching for arin.authdns.ripe.net. A record at rirns.arin.net. [199.253.249.53] ...took 155 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 b.gtld-servers.net. [192.33.14.30] ...took 13 ms
Searching for ns5.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 125 ms
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53]
...took 275 msSearching for ns5.yahoo.com. A record at b.gtld-servers.net. [192.33.14.30] ...took 13 ms
Searching for ns5.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 125 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 5 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 143 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 127 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 125 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 10 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 142 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 267 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
None of the nameservers responded correctly.
Total elapsed query time: 1,472 ms