Searching for 143.116.200.207.in-addr.arpa. PTR record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 7 ms
Searching for 143.116.200.207.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 129 ms
REFUSED
Searching for 143.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 119 ms
REFUSED
Searching for 143.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 187 ms
REFUSED
Searching for 143.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 19 ms
REFUSED
Searching for 143.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 13 ms
REFUSED
Searching for 143.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 143.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 123 ms
REFUSED
Searching for 143.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 189 ms
REFUSED
Searching for 143.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 143.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 143.116.200.207.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 129 ms
Searching for u.arin.net. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for u.arin.net. A record at h.gtld-servers.net. [192.54.112.30] ...took 6 ms
Searching for u.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 90 ms
Searching for 143.116.200.207.in-addr.arpa. PTR record at u.arin.net. [204.61.216.50]
...took 6 msSearching for u.arin.net. A record at h.gtld-servers.net. [192.54.112.30] ...took 6 ms
Searching for u.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 90 ms
Searching for ns3.yahoo.com. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 7 ms
Searching for ns3.yahoo.com. A record at d.gtld-servers.net. [192.31.80.30] ...took 24 ms
Searching for ns3.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
Searching for 143.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42]
...took 154 msSearching for ns3.yahoo.com. A record at d.gtld-servers.net. [192.31.80.30] ...took 24 ms
Searching for ns3.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 143.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 119 ms
REFUSED
Searching for 143.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 187 ms
REFUSED
Searching for 143.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 19 ms
REFUSED
Searching for 143.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 13 ms
REFUSED
Searching for 143.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 143.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 123 ms
REFUSED
Searching for 143.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 189 ms
REFUSED
Searching for 143.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 143.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,270 ms