Searching for 133.100.163.152.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for 133.100.163.152.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 14 ms
REFUSED
Searching for 133.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 133.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 257 ms
REFUSED
Searching for 133.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 143 ms
REFUSED
Searching for 133.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 133.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 133.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 262 ms
REFUSED
Searching for 133.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 133.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 130 ms
REFUSED
Searching for 133.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 142 ms
REFUSED
Searching for 133.100.163.152.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 14 ms
Searching for x.arin.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for x.arin.net. A record at b.gtld-servers.net. [192.33.14.30] ...took 12 ms
Searching for x.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 156 ms
Searching for 133.100.163.152.in-addr.arpa. PTR record at x.arin.net. [199.180.180.63]
...took 156 msSearching for x.arin.net. A record at b.gtld-servers.net. [192.33.14.30] ...took 12 ms
Searching for x.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 156 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 g.gtld-servers.net. [192.42.93.30] ...took 6 ms
Searching for ns4.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 128 ms
Searching for 133.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157]
...took 128 msSearching for ns4.yahoo.com. A record at g.gtld-servers.net. [192.42.93.30] ...took 6 ms
Searching for ns4.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 128 ms
REFUSED
Searching for 133.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 133.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 257 ms
REFUSED
Searching for 133.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 143 ms
REFUSED
Searching for 133.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 133.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 133.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 262 ms
REFUSED
Searching for 133.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 133.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 130 ms
REFUSED
Searching for 133.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,609 ms