Redirect Trace
Follow and display up to five HTTP redirects safely.
Read the guideRun the tool
JVR Software’s server processes the public target you enter. The diagnostic is rate-limited. Use a system you own or are authorised to check.
More information
Back to the toolWhat it is and when to use it
Redirect Trace shows the sequence of HTTP responses that moves a public URL to another address. It is useful during domain moves, when shortening a chain of old links, or when checking whether HTTP, HTTPS and alternate hostnames all arrive at the intended page.
How it works
The tool makes a HEAD request without automatic redirect handling, reads the Location header, resolves relative locations and repeats the request for a limited number of hops. Every next address is subject to the same public-target checks. The result includes the observed status and location at each recorded hop.
How to use it
- Enter the original URL, with the scheme and path as visitors use it.
- Run the trace and read the rows from the first requested URL to the last returned address.
- Compare the final location with the page you intended and use URL Status Checker for a GET comparison if the result seems inconsistent.
Worked example
Try https://jvrsoftware.co.za/apps/ to inspect the shop shortcut. The first hop should redirect to the SubmitJoy App Store. In your own migrations, test a deep link too so a prefix rule does not accidentally reroute a valid download or other child page.
Reading the result
301 and 308 signal a permanent move. 302 and 307 are normally temporary. A blank Location beside a non-redirect response generally marks the end. Look for repeated URLs, unnecessary hops, unexpected host changes and redirects back to plain HTTP.
Verify that a redirect preserves a query only when the new page needs it. A language parameter may have to survive the move, while an obsolete application parameter may be intentionally discarded. Put a harmless sample in the old URL and compare it with the Location values in each hop.
Common mistakes and limits
A HEAD response can differ from what a browser receives with GET. The tool stops after a bounded chain or when a request or target cannot be checked. Client-side JavaScript navigation and HTML refresh instructions are outside this HTTP-header trace.
