Manual-hop HTTP inspection
Redirect Trace Tool
Follow a public URL one redirect at a time and inspect each status, destination, and response time.
Only public HTTP(S) URLs are allowed. Private, loopback, link-local, and metadata destinations are blocked and every redirect destination is revalidated.
How to use the redirect trace tool
- STEP 1Enter a public website URL.
- STEP 2Follow each safe redirect up to ten hops.
- STEP 3Review or export the ordered chain as JSON.
About this tool
Trace a public HTTP redirect chain with manual redirect handling and safety validation before every destination request.
Relative Location headers are resolved against the response URL.
Timing measures each server response and is not a synthetic browser performance score.
Frequently asked questions
Which redirects are followed?
The tool follows HTTP responses from 300 through 399 when a Location header is present, resolving relative destinations against the current URL.
How many redirect hops are allowed?
Up to ten redirects are followed. Longer loops or chains return a redirect-limit error.
Are unsafe redirect targets fetched?
No. Every hop is DNS-checked before its request, and private, loopback, link-local, and metadata destinations are blocked.