Searching for 136.116.200.207.in-addr.arpa. PTR record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for 136.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
REFUSED
Searching for 136.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 136.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 229 ms
REFUSED
Searching for 136.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 136.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 130 ms
REFUSED
Searching for 136.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 19 ms
REFUSED
Searching for 136.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 225 ms
REFUSED
Searching for 136.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 10 ms
REFUSED
Searching for 136.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 136.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 136.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 H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for z.arin.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 23 ms
Searching for z.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 154 ms
Searching for 136.116.200.207.in-addr.arpa. PTR record at z.arin.net. [199.180.180.63]
...took 89 msSearching for z.arin.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 23 ms
Searching for z.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 154 ms
Searching for ns3.yahoo.com. A record at E.ROOT-SERVERS.NET. [192.203.230.10]
...took 7 ms
Searching for ns3.yahoo.com. A record at e.gtld-servers.net. [192.12.94.30] ...took 24 ms
Searching for ns3.yahoo.com. A record at ns5.yahoo.com. [202.165.97.53] ...took 186 ms
Searching for 136.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42]
...took 155 msSearching for ns3.yahoo.com. A record at e.gtld-servers.net. [192.12.94.30] ...took 24 ms
Searching for ns3.yahoo.com. A record at ns5.yahoo.com. [202.165.97.53] ...took 186 ms
REFUSED
Searching for 136.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 136.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 229 ms
REFUSED
Searching for 136.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 136.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 130 ms
REFUSED
Searching for 136.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 19 ms
REFUSED
Searching for 136.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 225 ms
REFUSED
Searching for 136.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 10 ms
REFUSED
Searching for 136.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 136.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,580 ms