Khalil Shreateh specializes in cybersecurity, particularly as a "white hat" hacker. He focuses on identifying and reporting security vulnerabilities in software and online platforms, with notable expertise in web application security. His most prominent work includes discovering a critical flaw in Facebook's system in 2013. Additionally, he develops free social media tools and browser extensions, contributing to digital security and user accessibility.

Get Rid of Ads!


Subscribe now for only $3 a month and enjoy an ad-free experience.

Contact us at khalil@khalil-shreateh.com

A screenshot of a Command Prompt window on Windows showing a tracert google.com command, displaying a route with hop numbers, IP addresses, and timing values in a classic black-and-white interface
Tracing the route to google.com with tracert on Windows

How I First Met traceroute

I stumbled upon traceroute years ago when a client’s website was loading painfully slow, and I needed to figure out why. This command became my window into the internet’s hidden routes, showing me every hop a data packet takes. It’s been a faithful tool ever since, and I’m eager to share what I’ve picked up along the way.

 

How I First Met traceroute

I stumbled upon traceroute years ago when a client’s website was loading painfully slow, and I needed to figure out why. This command became my window into the internet’s hidden routes, showing me every hop a data packet takes. It’s been a faithful tool ever since, and I’m eager to share what I’ve picked up along the way.

for site in google.com example.com; do
traceroute $site
done

This monitors multiple routes overnight. I’ve set it up for clients to catch intermittent issues.

Security Tips I Follow

I avoid running traceroute on sensitive networks without permission. I use trusted tools and watch for unusual hops that might indicate rerouting. Safety first keeps me out of trouble.

Comparing with Alternatives

ping tells me if a host is up, but traceroute shows the path. mtr combines both but needs extra setup. I stick with traceroute for its simplicity and reliability.

What I Love About It

  • It works on any system I own.
  • The output is easy to read.
  • It uncovers hidden network issues.
  • Options let me customize every run.

It’s a tool I grab instinctively.

Where It Falls Short

It can’t always reach the destination if blocked. Some routers hide details, leaving gaps. I supplement it with other tools when needed.

Real-Life Scenarios

I verify routes after DNS changes. I troubleshoot VPN lag with hop timings. I check server paths during migrations. It’s part of my daily toolkit.

Pro Tips from the Field

  • Pair it with ping for latency checks.
  • Use -n on busy networks to save time.
  • Test with different protocols if blocked.
  • Save output for later analysis.

These tricks have pulled me through tough spots.

The Future of traceroute

Despite newer tools, traceroute holds strong due to its ease. I expect minor updates for modern networks. It’s a classic I’ll keep using.

Combining with Other Tools

I use ping after tracert to test specific hops. With netstat, I check active connections. This combo gives me a full picture—once fixed a route with this approach.

A Tale from Work

Last week, a client’s site crawled. I ran tracert example.com and saw a 300ms delay at hop 7. A call to the ISP resolved a routing loop—problem solved.

Another Fix on the Go

An email server timed out, so I tried tracert to its IP. A timeout at hop 4 led me to a downed router. Switching providers fixed it in hours.

Wrapping Up My Experience

traceroute has been my guide through network mazes, from quick checks to deep dives. Its cross-platform power and clear output make it essential. Give it a try—it’ll change how you see the internet.

 

Found this article useful , Share it with your friends