Trace the network path to a public destination and view reverse DNS hostnames, IP registry details and registered location for each hop.
Traceroute shows the path packets take from the Zerolink server toward a destination. Each hop is a router or gateway along the route. When a website or server feels slow or unreachable, traceroute helps identify where the path changes or stops responding.
This tool enriches each hop with reverse DNS hostnames, IP registry information and registered location data using RDAP and public IP sources. That makes it easier to see whether delay appears inside an ISP network, at a transit provider or near the destination itself.
Results originate from the Zerolink server, not your own connection. Start with DNS lookup if naming is uncertain, then compare with ping for reachability, the internet speed test for connection performance, and the Network Diagnostics Suite for broader checks.
Use traceroute after DNS looks correct but performance or reachability is still uncertain.
Enter a public IP address or domain to map the route from the Zerolink server.
Test only destinations you own or are authorised to diagnose. Registry and location lookup uses RDAP and public IP data sources.
Interpret results carefully
Shows the round-trip time reported for the hop. Sudden increases often point to congestion or a long geographic segment.
Reverse DNS names help identify ISP routers, exchange points and hosting networks when PTR records are published.
Registration and ISP data show which organisation operates the IP range, useful when escalating routing issues.
Registered location helps identify the country or city associated with each hop when public geolocation data is available.
Intermediate routers may ignore traceroute probes by design. Focus on the last responding hop, compare with the ping tool for reachability, and use the internet speed test to measure your own connection latency.
The IP ping tool runs a quick reachability check with optional raw traceroute output. This page focuses on traceroute and adds reverse DNS hostnames, IP registry details and registered location for every hop in a structured table.
Registry information is looked up from RDAP registration data with a fallback to public IP geolocation providers when RDAP does not return an organisation name.
Location shows the registered or geolocated place associated with the hop IP, usually city, region and country when available from public IP data sources.
Many routers are configured not to reply to traceroute probes. A timeout on an intermediate hop does not always mean the path is broken.
A dash means no PTR reverse DNS record was available for that hop, or the router did not publish a resolvable hostname in the traceroute response.
No. Traceroute runs from the Zerolink web server. Routing and latency can differ from what you see on your own ISP connection.
No. Only public destinations are accepted. Private, local and reserved addresses are blocked for safety.
Up to 15 hops are requested per trace. Long paths may stop earlier if the destination responds sooner.
Use the internet speed test when you want to measure latency, download and upload on your own connection. Use traceroute when DNS and ping look fine but you need to see which network hops sit between the Zerolink server and the destination.
Both work. Testing a domain also shows current DNS A and AAAA records above the hop table, which is useful when a hostname recently changed.