IP Tools
Local test ready · production pending

Traceroute Test

Create one bounded network job and inspect only validated worker evidence.

Method:
Same-origin API → isolated network worker; explicit create, refresh and cancel only
Status:
idle

Input

Result

Ready

No job has been created. Complete the bounded form to begin.

One target and one bounded operation per job. No URL fetch, port range, custom resolver or browser-side probe is available.

Tool guide

Clear input, result, and evidence boundaries

See the bounded hop-by-hop path, latency, loss, and timed-out hops to one public target.

01

Input and method

One public hostname or IP, probe region, and an approved bounded trace method.

02

Reading the result

Each hop keeps its index, address or hostname, optional ASN or location summary, RTT, loss, and partial state.

03

Boundary and privacy

The trace is bounded and not a BGP view, global map, private-network scan, or unlimited monitor.

FAQ

Frequently asked questions

What does Traceroute Test check?

See the bounded hop-by-hop path, latency, loss, and timed-out hops to one public target.

What input does Traceroute Test accept?

One public hostname or IP, probe region, and an approved bounded trace method.

How should I interpret Traceroute Test results?

Each hop keeps its index, address or hostname, optional ASN or location summary, RTT, loss, and partial state.

What can Traceroute Test not prove?

The trace is bounded and not a BGP view, global map, private-network scan, or unlimited monitor.

How does Traceroute Test handle input and results?

Input is used only for this explicit check. The trace is bounded and not a BGP view, global map, private-network scan, or unlimited monitor.

When should I run Traceroute Test again?

Run it again after the relevant network, address, browser environment, or target changes. Each hop keeps its index, address or hostname, optional ASN or location summary, RTT, loss, and partial state.

Continue checking