Searching for 133.116.200.207.in-addr.arpa. PTR record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 37 ms
Searching for 133.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 92 ms
REFUSED
Searching for 133.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 186 ms
REFUSED
Searching for 133.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 7 ms
REFUSED
Searching for 133.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 133.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 133.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 133.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 132 ms
REFUSED
Searching for 133.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 191 ms
REFUSED
Searching for 133.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 188 ms
REFUSED
Searching for 133.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 133.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 92 ms
Searching for x.arin.net. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 37 ms
Searching for x.arin.net. A record at i.gtld-servers.net. [192.43.172.30] ...took 20 ms
Searching for x.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 143 ms
Searching for 133.116.200.207.in-addr.arpa. PTR record at x.arin.net. [199.180.180.63]
...took 90 msSearching for x.arin.net. A record at i.gtld-servers.net. [192.43.172.30] ...took 20 ms
Searching for x.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 143 ms
Searching for ns5.yahoo.com. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 37 ms
Searching for ns5.yahoo.com. A record at a.gtld-servers.net. [192.5.6.30] ...took 24 ms
Searching for ns5.yahoo.com. A record at ns5.yahoo.com. [202.165.97.53] ...took 198 ms
Searching for 133.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53]
...took 185 msSearching for ns5.yahoo.com. A record at a.gtld-servers.net. [192.5.6.30] ...took 24 ms
Searching for ns5.yahoo.com. A record at ns5.yahoo.com. [202.165.97.53] ...took 198 ms
REFUSED
Searching for 133.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 186 ms
REFUSED
Searching for 133.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 7 ms
REFUSED
Searching for 133.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 133.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 133.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 133.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 132 ms
REFUSED
Searching for 133.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 191 ms
REFUSED
Searching for 133.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 188 ms
REFUSED
Searching for 133.116.200.207.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,721 ms