HTTP Redirect Tracer
Follow every hop of a URL's redirect chain with status codes and final destination - to debug redirect loops, mixed 301/302 setups and SEO problems.
About HTTP Redirect Tracer
The HTTP Redirect Tracer requests a URL and follows each redirect manually, one hop at a time, recording the status code (301, 302, 307, 308...), the Location it points to and the server that answered. Instead of jumping straight to the final page like a browser, it shows you the whole path so you can see exactly how a request travels from start to destination.
This matters because redirects are a frequent source of subtle bugs: an HTTP-to-HTTPS redirect that loops, a chain that is one hop too long and slows every request, a temporary 302 used where a permanent 301 was intended (which dilutes SEO value), or a redirect that drops the path or query string. Seeing each hop and its status code turns these invisible problems into obvious ones.
The trace stops at the first non-redirect response and reports the final URL and status. It runs server-side from EU infrastructure and refuses redirects to private or internal addresses, so it is safe to point at any public URL.
How to use it
- 1Enter the starting URL (try the http:// version to see the HTTPS upgrade).
- 2Select Trace redirects.
- 3Read each hop in order: status code, current URL and where it redirects next.
- 4Check the number of hops and the final status - aim for a single 301 to the canonical HTTPS URL.
- 5Fix any loops, unnecessary hops or 302s that should be 301s on your server.
Common use cases
- -Debugging redirect loops that make a page fail to load.
- -Confirming HTTP reliably upgrades to HTTPS in one hop.
- -Checking that a site migration uses permanent 301 redirects for SEO.
- -Shortening long redirect chains that add latency.
- -Verifying a short link or campaign URL lands where it should.
Frequently asked questions
- What is the difference between a 301 and 302 redirect?
- A 301 is a permanent redirect - search engines transfer ranking to the new URL and browsers may cache it. A 302 (or 307) is temporary and passes no ranking. For a permanent move, always use 301.
- How many redirects are too many?
- Keep it to one hop where possible. Each redirect adds a round trip; chains of three or more noticeably slow the page and some crawlers stop following after several hops.
- Why is my HTTP-to-HTTPS redirect looping?
- A loop usually means a proxy or CDN terminates TLS and forwards HTTP internally, so the origin keeps redirecting to HTTPS. The tracer shows the repeating hop so you can fix the forwarded-protocol handling.
- Does the tracer follow redirects to internal addresses?
- No. For safety it refuses any hop that resolves to a private or reserved address, so it cannot be used to probe internal infrastructure.
- Can it trace non-GET redirects?
- It traces the GET redirect chain, which is what browsers and crawlers follow. 307 and 308 preserve the method, and they are reported with their status codes in the chain.