UNDERSTAND THE RESULT
How to trace a website redirect
A redirect tells a browser to request a different URL. It can be useful for HTTPS upgrades, moved pages and domain changes. A trace helps you see where the request goes and whether the chain ends with a useful response.
Start with these steps
- Paste the starting URL, including http:// or https:// when the distinction matters. Paths and query strings are accepted.
- Press Trace redirects. NetLuma requests each eligible destination separately and checks its public network address before connecting.
- Read the requests in order. Compare the final URL with the destination you expected, and inspect the last HTTP status.
Reading each hop
- 301 and 308 · permanent move
- The server says the resource has a new permanent location. Both codes can appear when a site moves to a different URL.
- 302 and 307 · temporary move
- The request is directed elsewhere temporarily. A 307 preserves the HTTP method; NetLuma’s trace uses GET requests.
- 303 · retrieve another resource
- Directs the client to retrieve a different resource with GET. It can appear after form-related workflows, although this tool does not submit forms.
- Final status · destination response
- Reaching a final URL is only part of the check. A final 404 or 500 still needs investigation; a 403 may indicate that the destination restricts automated requests.
- Loop or stopped chain · review the warning
- A repeated URL, a restricted destination or the six-request cap can stop the trace before a successful destination is reached.
What to try next
For your own website, compare the chain with your hosting redirects and application routing. After changing a redirect, test the original URL again. Use the SSL checker if the chain moves to a different HTTPS hostname.
Know the limits
The tool follows HTTP 301, 302, 303, 307 and 308 responses, with up to six requests. It does not execute JavaScript, follow HTML meta-refresh redirects or sign in to restricted pages.
Technical referencesMDN: Redirections in HTTP