Scanning Exercise

Perform a basic scan using standard tools such as ping, traceroute, dig and nslookup. Use these basic tools to compile a list that details the following information:

• How many hops from your machine to your assigned website? Tracing route to ec2-34-203-115-212.compute-1.amazonaws.com [34.203.115.212] over a maximum of 64 hops: 


  1     1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     7 ms     5 ms     4 ms  165-73-14-41.ip.afrihost.co.za [165.73.14.41]
  4     4 ms     3 ms     5 ms  169-1-21-232.ip.afrihost.co.za [169.1.21.232]
  5     4 ms     4 ms     5 ms  169-1-21-233.ip.afrihost.co.za [169.1.21.233]
  6   168 ms   167 ms   167 ms  te0-3-1-0.ccr51.jnb01.atlas.cogentco.com [206.249.0.169]
  7   167 ms   163 ms   163 ms  be2436.ccr21.lon02.atlas.cogentco.com [130.117.0.89]
  8   176 ms   163 ms   163 ms  be2572.ccr41.lon13.atlas.cogentco.com [154.54.61.253]
  9   230 ms   229 ms   229 ms  be2099.ccr31.bos01.atlas.cogentco.com [154.54.82.34]
 10   229 ms   229 ms   229 ms  38.140.158.98
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.
 31     *        *        *     Request timed out.
 32     *        *        *     Request timed out.
 33     *        *        *     Request timed out.
 34     *        *        *     Request timed out.
 35     *        *        *     Request timed out.
 36     *        *        *     Request timed out.
 37   244 ms   289 ms   242 ms  ec2-34-203-115-212.compute-1.amazonaws.com [34.203.115.212]

• Which step causes the biggest delay in the route? What is the average duration of that delay? 
37   244 ms   289 ms   242 ms  ec2-34-203-115-212.compute-1.amazonaws.com [34.203.115.212]
• What are the main nameservers for the website?
Name Server: ns-846.awsdns-41.net Name Server: ns-1235.awsdns-26.org Name Server: ns-1537.awsdns-00.co.uk Name Server: ns-416.awsdns-52.com

• Who is the registered contact?

Registrant Hostmaster, Amazon Legal Dept.

• What is the MX record for the website?

us-east-1.elasticbeanstalk.com primary name server = ns-59.awsdns-07.com responsible mail addr = awsdns-hostmaster.amazon.com

• Where is the website hosted?

Tech Name: Hostmaster, Amazon Legal Dept. Tech Organization: Amazon Technologies, Inc. Tech Street: P.O. Box 8102 Tech City: Reno Tech State/Province: NV Tech Postal Code: 89507 Tech Country: US Tech Phone: +1.2062664064 Tech Phone Ext: Tech Fax: +1.2062667010

• Did you have any issues or challenges with the scans?

Network scanning is not complicated and rather straightforward. What can be challenging is to correctly interpret the scanning outputs. We had a problem using the traceroute scanning tool. We had an issue where the trace would timeout by 30 hops which was the default settings on a windows machine.

• How did you overcome them?

We increased the default number of hops to 64 and reached a result at 37 hops,

• How will they affect your final report?

We noted that if a result is not reached, it is recommended to increase the parameters of our search in order to receive a result.