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 94 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 13 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 176 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 203 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 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 ns3.yahoo.com. [27.123.42.42] ...took 176 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 94 ms
Searching for r.arin.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for r.arin.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 22 ms
Searching for r.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 90 ms
Searching for 136.100.163.152.in-addr.arpa. PTR record at r.arin.net. [199.180.180.63]
...took 90 msSearching for r.arin.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 22 ms
Searching for r.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 90 ms
Searching for ns4.yahoo.com. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for ns4.yahoo.com. A record at b.gtld-servers.net. [192.33.14.30] ...took 37 ms
Searching for ns4.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157]
...took 131 msSearching for ns4.yahoo.com. A record at b.gtld-servers.net. [192.33.14.30] ...took 37 ms
Searching for ns4.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 13 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 176 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 203 ms
REFUSED
Searching for 136.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 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 ns3.yahoo.com. [27.123.42.42] ...took 176 ms
REFUSED
Searching for 136.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,428 ms