Searching for 134.100.163.152.in-addr.arpa. PTR record at D.ROOT-SERVERS.NET. [199.7.91.13]
...took 11 ms
Searching for 134.100.163.152.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 12 ms
REFUSED
Searching for 134.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 134.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 142 ms
REFUSED
Searching for 134.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 134.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 252 ms
REFUSED
Searching for 134.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 121 ms
REFUSED
Searching for 134.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 256 ms
REFUSED
Searching for 134.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 134.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 134.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 142 ms
REFUSED
Searching for 134.100.163.152.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 12 ms
Searching for arin.authdns.ripe.net. A record at D.ROOT-SERVERS.NET. [199.7.91.13]
...took 11 ms
Searching for arin.authdns.ripe.net. A record at g.gtld-servers.net. [192.42.93.30] ...took 6 ms
Searching for arin.authdns.ripe.net. A record at manus.authdns.ripe.net. [193.0.9.7] ...took 11 ms
Searching for 134.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 g.gtld-servers.net. [192.42.93.30] ...took 6 ms
Searching for arin.authdns.ripe.net. A record at manus.authdns.ripe.net. [193.0.9.7] ...took 11 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 11 ms
Searching for ns4.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
Searching for 134.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157]
...took 122 msSearching for ns4.yahoo.com. A record at k.gtld-servers.net. [192.52.178.30] ...took 11 ms
Searching for ns4.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 134.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 134.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 142 ms
REFUSED
Searching for 134.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 134.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 252 ms
REFUSED
Searching for 134.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 121 ms
REFUSED
Searching for 134.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 256 ms
REFUSED
Searching for 134.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 134.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 134.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 142 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,161 ms