Real HTTP requests
The checker uses GET requests because some servers respond differently to HEAD. It reads only a small, capped portion of each response.
HTTP trace · every hop explained
Follow a website redirect from first request to final page.
See each 301, 302, 307 or 308 response in order. Find loops, failed destinations, HTTPS downgrades and extra hops that make a route slower or harder to maintain.
Trace a websiteStart with any public page
Where should the trace begin?
Enter a domain or full page address. We will follow the same Location instructions a browser receives and lay out the path in order.
The checker follows public HTTP and HTTPS addresses on standard web ports, with a limit of ten redirects.
A cleaner route
Keep the necessary redirect. Remove the sightseeing tour.
A deliberate move from an old address to its current destination is useful. Multiple legacy rules chained together add requests, delay and more places for a future change to break.
DIRECT
OLD URLFINAL URL
One clear instructionDETOUR
OLD URLHOPHOPFINAL
Extra requests and rulesHow to read this trace
One check can show the route—not every visitor's experience.
Every hop checked
Each destination is resolved and validated before it is contacted. The trace follows public HTTP or HTTPS addresses on ports 80 and 443.
Ten-redirect limit
The trace stops after ten redirects, on a loop, on a missing Location header, or when a destination cannot be safely reached.
One point of view
CDN rules, location, cookies, device type and user agent can make another visitor receive a different route.
Status and Location handling follow the HTTP semantics defined in RFC 9110 .
Redirect questions
Know what the status codes are telling you.
What is a redirect chain?
It is a sequence in which one URL sends a browser to another URL, which may then redirect again before a final response is reached.
Are all website redirects bad?
No. One deliberate redirect is common when moving from HTTP to HTTPS or from an old page to its replacement. Unnecessary extra hops add delay and complexity.
Why review an HTTPS-to-HTTP redirect?
It sends a visitor from an encrypted address to an unencrypted one. That weakens the path and is usually a configuration choice worth correcting.
Will every visitor see exactly the same redirects?
Not always. Redirects can vary by location, device, cookies, user agent, CDN rules or application state. This result is one server-side observation at the time shown.
How do 301, 302, 307 and 308 differ?
301 and 308 indicate permanent redirects, while 302 and 307 indicate temporary redirects. The 307 and 308 codes explicitly preserve the original request method.