Follow the network path to a server, hop by hop

With Traceroute, web developers and site testers can inspect routing hops to a server during troubleshooting. Follow the network path to a server, hop by hop.

Follow the network path to a server, hop by hop. The tool is free in your browser and shows the result without asking you to create an account.

How to use

Enter the domain you want to trace in the input field, without adding a protocol or path unless the tool asks for it.
Start the test so the request is made by the YOORfree server to the target.
Look at the hops shown and identify those that respond slowly or not at all.
Compare the path with your expectations to decide whether the issue is network-related, a firewall rule or the target itself.

Example

A web developer receives complaints that a site is slow from one region. They enter the domain, run the traceroute and review the hops to see whether the delay appears early in the path or close to the final server.

Limits and formats

A traceroute shows one possible path at the time of the test; routers may take different routes depending on traffic.
Some devices do not answer diagnostic packets, leaving blank hops that do not by themselves prove an outage.
The result can differ between two runs and does not replace continuous monitoring.
Testing from the outside may not reproduce the internal network of a user or an office.

Where processing happens

The domain you enter is sent to the YOORfree server. That server then runs the traceroute towards the target and returns the observed hops to you. No file is uploaded during the operation.

Frequently asked questions

Why do some hops appear empty or show a star?

Routers or firewalls may refuse to answer the packets used by traceroute. This does not always mean the path is broken, but it can make the result harder to read.

Can I trace an internal company domain?

The test starts from an external server. A domain available only from your internal network will probably not be reachable, and the result will not reflect your local configuration.

Does traceroute always show the exact path?

No. Routing can change with traffic and operator decisions. The result gives a useful snapshot, not a permanent map of the network.