Searching for 105.116.200.207.in-addr.arpa. PTR record at E.ROOT-SERVERS.NET. [192.203.230.10]
...took 6 ms
Searching for 105.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
REFUSED
Searching for 105.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 105.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 105.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 105.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 122 ms
REFUSED
Searching for 105.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 105.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 105.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 105.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 188 ms
REFUSED
Searching for 105.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 130 ms
REFUSED
Searching for 105.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
Searching for z.arin.net. A record at B.ROOT-SERVERS.NET. [192.228.79.201]
...took 18 ms
Searching for z.arin.net. A record at g.gtld-servers.net. [192.42.93.30] ...took 7 ms
Searching for z.arin.net. A record at u.arin.net. [204.61.216.50] ...took 6 ms
Searching for 105.116.200.207.in-addr.arpa. PTR record at z.arin.net. [199.180.180.63]
...took 94 msSearching for z.arin.net. A record at g.gtld-servers.net. [192.42.93.30] ...took 7 ms
Searching for z.arin.net. A record at u.arin.net. [204.61.216.50] ...took 6 ms
Searching for ns5.yahoo.com. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 31 ms
Searching for ns5.yahoo.com. A record at f.gtld-servers.net. [192.35.51.30] ...took 7 ms
Searching for ns5.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
Searching for 105.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53]
...took 185 msSearching for ns5.yahoo.com. A record at f.gtld-servers.net. [192.35.51.30] ...took 7 ms
Searching for ns5.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 105.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 105.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 105.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 105.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 122 ms
REFUSED
Searching for 105.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 105.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 105.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 105.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 188 ms
REFUSED
Searching for 105.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 130 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,172 ms