Searching for 88.116.200.207.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for 88.116.200.207.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 165 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 145 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 116 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 167 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 144 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 193 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 131 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 165 ms
Searching for z.arin.net. A record at E.ROOT-SERVERS.NET. [192.203.230.10]
...took 32 ms
Searching for z.arin.net. A record at e.gtld-servers.net. [192.12.94.30] ...took 23 ms
Searching for z.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 143 ms
Searching for 88.116.200.207.in-addr.arpa. PTR record at z.arin.net. [199.180.180.63]
...took 93 msSearching for z.arin.net. A record at e.gtld-servers.net. [192.12.94.30] ...took 23 ms
Searching for z.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 143 ms
Searching for ns1.yahoo.com. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns1.yahoo.com. A record at l.gtld-servers.net. [192.41.162.30] ...took 12 ms
Searching for ns1.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 145 ms
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16]
...took 20 msSearching for ns1.yahoo.com. A record at l.gtld-servers.net. [192.41.162.30] ...took 12 ms
Searching for ns1.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 145 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 145 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 116 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 167 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 144 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 193 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 131 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,579 ms