Searching for 80.116.200.207.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for 80.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 100 ms
REFUSED
Searching for 80.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 80.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] Timed out while trying to resolve 80.116.200.207.in-addr.arpa./PTR, id=1321
Searching for 80.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 131 ms
REFUSED
Searching for 80.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 80.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 80.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 180 ms
REFUSED
Searching for 80.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 143 ms
REFUSED
Searching for 80.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 128 ms
REFUSED
Searching for 80.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 80.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 100 ms
Searching for arin.authdns.ripe.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for arin.authdns.ripe.net. A record at h.gtld-servers.net. [192.54.112.30] ...took 7 ms
Searching for arin.authdns.ripe.net. A record at rirns.arin.net. [199.253.249.53] ...took 94 ms
Searching for 80.116.200.207.in-addr.arpa. PTR record at arin.authdns.ripe.net. [193.0.9.10]
...took 11 msSearching for arin.authdns.ripe.net. A record at h.gtld-servers.net. [192.54.112.30] ...took 7 ms
Searching for arin.authdns.ripe.net. A record at rirns.arin.net. [199.253.249.53] ...took 94 ms
Searching for ns3.yahoo.com. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns3.yahoo.com. A record at c.gtld-servers.net. [192.26.92.30] ...took 23 ms
Searching for ns3.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
Searching for 80.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42]
...took 143 msSearching for ns3.yahoo.com. A record at c.gtld-servers.net. [192.26.92.30] ...took 23 ms
Searching for ns3.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 80.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 80.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] Timed out while trying to resolve 80.116.200.207.in-addr.arpa./PTR, id=1321
Searching for 80.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 131 ms
REFUSED
Searching for 80.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 80.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 80.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 180 ms
REFUSED
Searching for 80.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 143 ms
REFUSED
Searching for 80.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 128 ms
REFUSED
Searching for 80.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 3,049 ms