Using Ping and Traceroute to see travel between websites

 Working with ping and traceroute analyses of three distinct websites, each offers unique insights into their connectivity dynamics. The initial website was www.google.com, exhibiting a swift ping response as it efficiently received all 4 packets within the 24-25 milliseconds timeframe. The traceroute for Google's website unfolded seamlessly, navigating through 13 hops without encountering any disruptions. Moving on to our school's student portal website, student.uagc.edu, the ping for this site was slower compared to Google, clocking in at approximately 32 milliseconds. However, the traceroute for the student portal proceeded smoothly, going through 12 destinations without encountering any hops or interruptions. The final website subjected to this analysis was a government website, www.state.gov. Notably, this site presented the slowest ping response, reaching up to 67 milliseconds. The traceroute for the government website, while successful, exhibited two misses out of the 18 hops conducted. This raises questions about potential restrictions or blocks implemented on the government site, contributing to its slower response time and incomplete traceroute. Extensive research through Google searches unveiled that traceroute hops might be missed or remain incomplete due to the presence of firewalls or router blocks. The observed variations in ping and traceroute results across these websites prompt further inquiry into the underlying factors influencing their connectivity profiles. The unique challenges faced by the government website, by missed hops and a comparatively slower ping, suggest heightened security measures, potentially in the form of restrictive firewalls or router blocks. As the digital landscape continues to evolve, these analyses provide valuable insights.

The following will show Ping and Traceroute for the following three websites: www.google.com,  student.uagc.edu, and www.state.gov