Searching for 88.116.200.207.in-addr.arpa. PTR record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 7 ms
Searching for 88.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 93 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 10 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 128 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 265 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 10 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 93 ms
Searching for arin.authdns.ripe.net. A record at E.ROOT-SERVERS.NET. [192.203.230.10]
...took 7 ms
Searching for arin.authdns.ripe.net. A record at m.gtld-servers.net. [192.55.83.30] ...took 13 ms
Searching for arin.authdns.ripe.net. A record at ns3.lacnic.net. [200.3.13.14] ...took 194 ms
Searching for 88.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 m.gtld-servers.net. [192.55.83.30] ...took 13 ms
Searching for arin.authdns.ripe.net. A record at ns3.lacnic.net. [200.3.13.14] ...took 194 ms
Searching for ns5.yahoo.com. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 7 ms
Searching for ns5.yahoo.com. A record at m.gtld-servers.net. [192.55.83.30] ...took 12 ms
Searching for ns5.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53]
...took 266 msSearching for ns5.yahoo.com. A record at m.gtld-servers.net. [192.55.83.30] ...took 12 ms
Searching for ns5.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 10 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 128 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 265 ms
REFUSED
Searching for 88.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 10 ms
REFUSED
Searching for 88.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,493 ms