Searching for 196.116.200.207.in-addr.arpa. PTR record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 30 ms
Searching for 196.116.200.207.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 6 ms
REFUSED
Searching for 196.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 196.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 196.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 145 ms
REFUSED
Searching for 196.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 129 ms
REFUSED
Searching for 196.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 10 ms
REFUSED
Searching for 196.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 196.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 178 ms
REFUSED
Searching for 196.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 145 ms
REFUSED
Searching for 196.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 196.116.200.207.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 6 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 g.gtld-servers.net. [192.42.93.30] ...took 7 ms
Searching for x.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 147 ms
Searching for 196.116.200.207.in-addr.arpa. PTR record at x.arin.net. [199.180.180.63]
...took 91 msSearching for x.arin.net. A record at g.gtld-servers.net. [192.42.93.30] ...took 7 ms
Searching for x.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 147 ms
Searching for ns5.yahoo.com. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns5.yahoo.com. A record at e.gtld-servers.net. [192.12.94.30] ...took 23 ms
Searching for ns5.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
Searching for 196.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53]
...took 183 msSearching for ns5.yahoo.com. A record at e.gtld-servers.net. [192.12.94.30] ...took 23 ms
Searching for ns5.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 196.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 196.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 196.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 145 ms
REFUSED
Searching for 196.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 129 ms
REFUSED
Searching for 196.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 10 ms
REFUSED
Searching for 196.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 196.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 178 ms
REFUSED
Searching for 196.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 145 ms
REFUSED
Searching for 196.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,290 ms