Searching for 76.116.200.207.in-addr.arpa. PTR record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 39 ms
Searching for 76.116.200.207.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 169 ms
REFUSED
Searching for 76.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 122 ms
REFUSED
Searching for 76.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 188 ms
REFUSED
Searching for 76.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 76.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 186 ms
REFUSED
Searching for 76.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 132 ms
REFUSED
Searching for 76.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 194 ms
REFUSED
Searching for 76.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 76.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 200 ms
REFUSED
Searching for 76.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 10 ms
REFUSED
Searching for 76.116.200.207.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 169 ms
Searching for z.arin.net. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 40 ms
Searching for z.arin.net. A record at b.gtld-servers.net. [192.33.14.30] ...took 40 ms
Searching for z.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 92 ms
Searching for 76.116.200.207.in-addr.arpa. PTR record at z.arin.net. [199.180.180.63]
...took 90 msSearching for z.arin.net. A record at b.gtld-servers.net. [192.33.14.30] ...took 40 ms
Searching for z.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 92 ms
Searching for ns1.yahoo.com. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 39 ms
Searching for ns1.yahoo.com. A record at m.gtld-servers.net. [192.55.83.30] ...took 13 ms
Searching for ns1.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
Searching for 76.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16]
...took 13 msSearching for ns1.yahoo.com. A record at m.gtld-servers.net. [192.55.83.30] ...took 13 ms
Searching for ns1.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 76.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 122 ms
REFUSED
Searching for 76.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 188 ms
REFUSED
Searching for 76.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 76.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 186 ms
REFUSED
Searching for 76.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 132 ms
REFUSED
Searching for 76.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 194 ms
REFUSED
Searching for 76.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 76.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 200 ms
REFUSED
Searching for 76.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 10 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,591 ms