Searching for 136.100.163.152.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for 136.100.163.152.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 91 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 119 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 173 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 128 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 181 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 148 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 91 ms
Searching for arin.authdns.ripe.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for arin.authdns.ripe.net. A record at c.gtld-servers.net. [192.26.92.30] ...took 24 ms
Searching for arin.authdns.ripe.net. A record at ns4.apnic.net. [202.12.31.53] ...took 16 ms
Searching for 136.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 c.gtld-servers.net. [192.26.92.30] ...took 24 ms
Searching for arin.authdns.ripe.net. A record at ns4.apnic.net. [202.12.31.53] ...took 16 ms
Searching for ns3.yahoo.com. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for ns3.yahoo.com. A record at a.gtld-servers.net. [192.5.6.30] ...took 23 ms
Searching for ns3.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42]
...took 149 msSearching for ns3.yahoo.com. A record at a.gtld-servers.net. [192.5.6.30] ...took 23 ms
Searching for ns3.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 119 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 173 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 128 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 181 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 148 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,285 ms