HTTP redirect checker.
Follow a public page through its HTTP redirects. See every response, destination, and hop timing, then confirm where a complete chain ends.
A closer look at a public URL. Checked by our server, with recent results reused for up to five minutes.
Follow each HTTP redirect.
Privacy & fair-use limits
Fresh network inspections are limited to 5 per minute, 20 per hour and 40 per day per IP. Cached responses have a separate limit of 60 requests per minute per IP. The authorized signed-in owner has a separate 100 fresh inspections/day allowance; the shared service limit is 1,000 per day. Your URL is sent to our server; it is not added to browser history or a public report. We do not forward credentials, and recognized sensitive header values are redacted. Avoid private links or URLs containing secrets. Data handling details
Each hop is one server response.
When checked, each bar represents the observed response time for one HTTP hop, including network and CDN. It is not full page-load time.
- Request the starting URL
The server follows HTTP response redirects only, up to the tool limit.
- Read each response
Status, destination and per-hop response time are shown when measured.
- Stop at the final response
This is not a browser page-load measurement and does not load assets.
One server request
This is a server request, not a browser. It does not run JavaScript, load assets, or include browser cookies and login state.
HTTP redirects only
We follow bounded HTTP response redirects. JavaScript navigation and HTML meta refresh are not followed.
Public pages only
Credentials are not sent. Private or restricted destinations are blocked, and sensitive response header values are redacted.
How to check a redirect chain.
- Enter a public HTTP or HTTPS address and start the inspection.
- Read each response code and destination in order. Expand a hop to see its response headers.
- When the chain completes, confirm the final destination. A blocked or limited route is shown as partial.
Hop timing includes the network and CDN and is not an isolated server benchmark. Check response headers with the HTTP header viewer, or measure page weight with the page weight budget.
Does this follow JavaScript or meta refresh redirects?
No. The checker follows HTTP response redirects only. It does not run JavaScript or inspect HTML meta refresh instructions.
Why might a redirect chain stop early?
The checker limits the chain to five redirects, enforces a request timeout, and blocks private or restricted destinations. A partial result is not labeled as the final destination.
Is the final URL always where a browser lands?
Not always. Browsers can apply JavaScript navigation, cookies, authentication, geolocation, and other behavior this server-side GET request does not reproduce.