Redirect Trace follows every hop in an HTTP redirect chain from the starting URL to the final destination, recording the status code, Location header and timing of each hop so you can see exactly how a URL resolves.
Enter a URL (http://example.org) and run the tool. The probe follows each redirect until a non-redirect response is received or a limit is reached.
Input: URL — e.g. http://example.org.
Each line shows a hop: the status code (301, 302, 307, 308), the Location header the server returned, and the time that hop took. The final line is the destination that loads in a browser. Long chains slow users down and dilute SEO ranking; redirect loops (detected automatically) break the page entirely.
→ Trace a URL through its full redirect chain to the final destination.
→ Confirm a 301 migration passes to the correct final URL.
→ Detect and fix redirect loops after a config change.
→ Measure the latency cost of multi-hop redirect chains.
301 and 308 are permanent; 302 and 307 are temporary. 307 and 308 preserve the original request method (POST stays POST), while 301/302 historically let clients change POST to GET. Use 301/308 for permanent moves to preserve SEO equity.
A single 301 to the new URL passes link equity cleanly. Long chains (multiple hops) dilute equity and add latency, and chains that mix protocols or domains can lose ranking signals. Flatten chains to a single hop where possible.
Two URLs redirecting to each other, or a URL redirecting to itself — often caused by forcing HTTPS while the reverse proxy rewrites back to HTTP, or conflicting rules. The tool detects loops automatically so you can fix the conflicting rule.