Skip to main content
ToolsHub

Traceroute

Enter a hostname to trace the full network route, showing each hop and its response time.

May take up to 30 seconds — traces up to 15 hops.

Traceroute runs on our servers. Results reflect the network path from our infrastructure.

How to use Traceroute

The Traceroute tool maps the path that packets take from a source to a destination host, listing each router (hop) along the way and the latency to reach it. Where ping tells you only the round-trip time to the far end, traceroute reveals the whole journey, exposing exactly where a connection slows down or breaks. Use this tool to diagnose why a server feels distant, to pinpoint which network along the route is dropping packets or adding delay, and to understand the geography and providers your traffic crosses to get there.

  1. Enter the destination hostname or IP address.
  2. Click Trace to map the route hop by hop.
  3. Read each hop’s address and round-trip latency.
  4. Look for the hop where latency jumps or replies stop.
  5. Use the failing hop to localise the problem along the path.

How traceroute maps the path

Traceroute sends packets with a deliberately small time-to-live value that increases by one each round. The first packet expires at the first router, which reports back; the next expires at the second, and so on, so the replies trace out every hop between you and the destination. The latency to each hop shows where delay accumulates. A steady rise in latency across hops is normal as distance grows; a sudden large jump at one hop, sustained for the rest of the path, marks where a slow or congested link sits.

Reading stars and dead ends

Hops that show asterisks instead of times mean a router did not reply, which is often harmless: many routers deprioritise or block the diagnostic packets traceroute relies on, so a starred middle hop while later hops respond is nothing to worry about. What matters is where the trace stops completely. If replies cease partway and never resume, the problem likely lies at or just beyond the last responding hop. Identifying that point tells you which network — yours, an intermediate provider, or the destination’s — to investigate or report to.

Interpreting hops
ObservationLikely meaning
Gradual latency riseNormal distance increase
Sudden sustained jumpCongested or distant link
Asterisks then recoveryRouter silently skips diagnostics
Trace stops entirelyFailure at or beyond last hop

Glossary

Traceroute
A tool that maps the routers along the path to a destination.
Hop
A single router the packet passes through on its way.
TTL
Time to live — a counter that limits how many hops a packet can take.
Round-trip time
The latency to reach a hop and receive its reply.
Asterisk hop
A hop that did not reply, often because diagnostics are blocked.

Related reading

Frequently Asked Questions

Free · No spam

Get weekly tool tips & updates

New tools, power-user tips, and productivity hacks — delivered free every Friday.

No spam, ever. Unsubscribe with one click.

Why use Traceroute?

  • Real-time DNS lookups using live resolver queries
  • Supports IPv4 and IPv6 addresses
  • No software to install — runs entirely in the browser
  • Results include TTL values and record priority

Common use cases

  • Verify DNS propagation after updating nameservers
  • Check MX records when troubleshooting email delivery
  • Look up SPF/DKIM/DMARC records for email security audits
  • Test whether a SSL certificate is valid and up to date
  • Find the IP address behind a domain name

Related Network & DNS

Explore all Network & DNS.