Searching for 3.116.200.207.in-addr.arpa. PTR record at B.ROOT-SERVERS.NET. [192.228.79.201]
...took 18 ms
Searching for 3.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 12 ms
REFUSED
Searching for 3.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 306 ms
REFUSED
Searching for 3.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 3.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 3.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 3.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 268 ms
REFUSED
Searching for 3.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 3.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 121 ms
REFUSED
Searching for 3.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 3.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 3.116.200.207.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 H.ROOT-SERVERS.NET. [198.97.190.53]
...took 7 ms
Searching for arin.authdns.ripe.net. A record at g.gtld-servers.net. [192.42.93.30] ...took 7 ms
Searching for arin.authdns.ripe.net. A record at rirns.arin.net. [199.253.249.53] ...took 90 ms
Searching for 3.116.200.207.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 7 ms
Searching for arin.authdns.ripe.net. A record at rirns.arin.net. [199.253.249.53] ...took 90 ms
Searching for ns4.yahoo.com. A record at D.ROOT-SERVERS.NET. [199.7.91.13]
...took 6 ms
Searching for ns4.yahoo.com. A record at d.gtld-servers.net. [192.31.80.30] ...took 24 ms
Searching for ns4.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
Searching for 3.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157]
...took 124 msSearching for ns4.yahoo.com. A record at d.gtld-servers.net. [192.31.80.30] ...took 24 ms
Searching for ns4.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 3.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 306 ms
REFUSED
Searching for 3.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 3.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 3.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 3.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 268 ms
REFUSED
Searching for 3.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 3.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 121 ms
REFUSED
Searching for 3.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 3.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,493 ms