Searching for 185.231.14.78.in-addr.arpa. PTR record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 34 ms
Searching for 185.231.14.78.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] Timed out while trying to resolve 185.231.14.78.in-addr.arpa./PTR, id=20780
Searching for 185.231.14.78.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 7 ms
Searching for 185.231.14.78.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] Timed out while trying to resolve 185.231.14.78.in-addr.arpa./PTR, id=20780
Searching for 185.231.14.78.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 7 ms
Searching for ns4.apnic.net. A record at F.ROOT-SERVERS.NET. [192.5.5.241]
...took 6 ms
Searching for ns4.apnic.net. A record at c.gtld-servers.net. [192.26.92.30] ...took 24 ms
Searching for ns4.apnic.net. A record at ns1.apnic.net. [203.119.42.53] ...took 166 ms
Searching for 185.231.14.78.in-addr.arpa. PTR record at ns4.apnic.net. [202.12.31.53]
...took 16 msSearching for ns4.apnic.net. A record at c.gtld-servers.net. [192.26.92.30] ...took 24 ms
Searching for ns4.apnic.net. A record at ns1.apnic.net. [203.119.42.53] ...took 166 ms
Searching for ns3-16-mx-central-1.ec2-rdns.amazonaws.com. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 34 ms
Searching for ns3-16-mx-central-1.ec2-rdns.amazonaws.com. A record at d.gtld-servers.net. [192.31.80.30] ...took 24 ms
Searching for ns3-16-mx-central-1.ec2-rdns.amazonaws.com. A record at ns4-ec2-rdns.amazonaws.com. [205.251.194.100] ...took 40 ms
Searching for 185.231.14.78.in-addr.arpa. PTR record at ns3-16-mx-central-1.ec2-rdns.amazonaws.com. [205.251.193.162]
...took 27 msSearching for ns3-16-mx-central-1.ec2-rdns.amazonaws.com. A record at d.gtld-servers.net. [192.31.80.30] ...took 24 ms
Searching for ns-1670.awsdns-16.co.uk. A record at F.ROOT-SERVERS.NET. [192.5.5.241]
...took 7 ms
Searching for ns-1670.awsdns-16.co.uk. A record at nsb.nic.uk. [156.154.101.3] ...took 6 ms
Searching for ns-1670.awsdns-16.co.uk. A record at g-ns-336.awsdns-16.co.uk. [205.251.193.80] ...took 28 ms
Searching for ns3-16-mx-central-1.ec2-rdns.amazonaws.com. A record at ns-1670.awsdns-16.co.uk. [205.251.198.134]
...took 12 msSearching for ns-1670.awsdns-16.co.uk. A record at nsb.nic.uk. [156.154.101.3] ...took 6 ms
Searching for ns-1670.awsdns-16.co.uk. A record at g-ns-336.awsdns-16.co.uk. [205.251.193.80] ...took 28 ms
Searching for ns3-16-mx-central-1.ec2-rdns.amazonaws.com. A record at ns4-ec2-rdns.amazonaws.com. [205.251.194.100] ...took 40 ms
Searching for ns1-24-mx-central-1.ec2-rdns.amazonaws.com. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 34 ms
Searching for ns1-24-mx-central-1.ec2-rdns.amazonaws.com. A record at l.gtld-servers.net. [192.41.162.30] ...took 11 ms
Searching for ns1-24-mx-central-1.ec2-rdns.amazonaws.com. A record at ns-27.awsdns-03.com. [205.251.192.27] ...took 27 ms
Searching for ns1-24-mx-central-1.ec2-rdns.amazonaws.com. A record at ns4-ec2-rdns.amazonaws.com. [205.251.194.100] ...took 6 ms
Searching for 185.231.14.78.in-addr.arpa. PTR record at ns1-24-mx-central-1.ec2-rdns.amazonaws.com. [205.251.196.131]
...took 22 msSearching for ns1-24-mx-central-1.ec2-rdns.amazonaws.com. A record at l.gtld-servers.net. [192.41.162.30] ...took 11 ms
Searching for ns1-24-mx-central-1.ec2-rdns.amazonaws.com. A record at ns-27.awsdns-03.com. [205.251.192.27] ...took 27 ms
Searching for ns1-24-mx-central-1.ec2-rdns.amazonaws.com. A record at ns4-ec2-rdns.amazonaws.com. [205.251.194.100] ...took 6 ms
| Domain | Type | TTL | Answer |
|---|---|---|---|
| 185.231.14.78.in-addr.arpa. | PTR | 300 | ec2-78-14-231-185.mx-central-1.compute.amazonaws.com. |
Total elapsed query time: 2,532 ms