Keep the exact shared URL
Paste the address exactly as received, including its query string. A short link or tracking parameter may change the path; the example button fills a URL without sending it.
HTTP & Request Debugging
Enter one public HTTP or HTTPS URL. A check starts only when you choose to send it.
The hop report will appear here after a check.
When you click Check, the URL is sent to this site service, which requests the public target. The target sees that request; avoid private links or tokens in the URL.
Manual GET only · standard HTTP/HTTPS ports · at most 10 redirects. No cookies or custom headers are sent.
Enter a public URL to begin.
A redirect checker is useful when an old URL loads but you cannot tell which server moved it, whether a short link crosses another domain, or why the destination is slow. The browser usually hides the intermediate responses.
This URL redirect checker asks the site service to make a fixed GET request and report each HTTP response. Compare the raw Location with the resolved next URL before deciding which rule or link to change.
Keep the observed path and the moment it was observed together.
The redirect checker records every status, original Location header and resolved next address. A redirect chain checker that only prints the final page cannot show which hop introduced an unwanted host or extra latency.
If a Location points toward a private, local or reserved destination, tracing stops before requesting it. The partial chain stays visible and has no invented final URL; the same check runs again for every public hostname.
Paste the address exactly as received, including its query string. A short link or tracking parameter may change the path; the example button fills a URL without sending it.
The check is manual because it sends the URL to this site service and makes a public network request. You can also press Ctrl or Cmd plus Enter; changing the input never silently resends it.
A final status can be 200 or 404 and still be a complete trace. A loop, blocked target, missing Location or hop limit gives a partial report, so inspect the last observed hop before exporting.
The 301 redirect checker distinguishes a permanent 301 or 308 from a temporary 302 or 307. It shows the raw Location and the absolute URL resolved from a relative value.
A repeated URL stops the trace. If a hop moves from HTTPS back to HTTP, the report flags the downgrade instead of treating the final page alone as proof of a secure route.
Each report includes its check time, per-hop response time, redirect count and termination reason. Copy or download only a fresh report; editing the URL disables both export actions.
Run the original URL and read the first hop. A 301 response with a Location confirms that specific GET returned a permanent redirect at the recorded time.
A chain has more than one redirect before the endpoint. The report lists the intermediate URLs and times, letting you point an old rule directly at the intended destination when you control it.
301 and 308 signal permanent moves; 302 and 307 are temporary. The latter pair also preserve the method for non-GET requests, but this tool deliberately tests GET only.
A repeated normalized URL is marked as a loop. Compare the last two rules, especially HTTP versus HTTPS or www versus non-www settings; the tool does not edit the server rules.
Yes. Enter the HTTP URL and check the first Location for an HTTPS target. A later HTTPS-to-HTTP hop is flagged as a downgrade; the report describes only this service-side request.
Does a hop look wrong?
Check one public URL now, then keep the time-stamped JSON beside the rule you plan to fix.