Feature
Redirect Checker
Enter a URL and see every redirect it passes through: the status code, location and timing of each hop, and the page it finally reaches.
Browsers follow redirects without showing you the route. The redirect checker does the opposite: it requests the URL, records each response, and follows the Location header one hop at a time until it reaches a page that isn’t a redirect.
What each hop shows
- The status code: 301 and 308 are permanent, 302, 303 and 307 are temporary
- The Location the server sent, including any change of domain or protocol
- How long that step took
- Whether the chain ended in a page, an error, a loop or the hop limit
Hop limit and loops
You can set how many hops to follow, up to 10 on the free plan. If a URL comes back to one it already visited, the check stops instead of following it forever and marks the result as a redirect loop, under Broken and its own Redirect loops filter.
Limits to keep in mind
Redirects set by JavaScript or a meta refresh after the page loads aren’t HTTP redirects and may not appear.
Some servers redirect differently depending on location, device or cookies.
Checks need a free account, and each URL uses one check from your daily allowance.
Common questions
- Why does my URL redirect twice?
- A common pattern is http to https, then the bare domain to www (or the reverse). Point both straight at the final version to make it one hop.
- Can I check many redirects at once?
- Yes. Paste a list and every URL is traced. Each URL uses one check from your daily allowance, which is 250 on the free plan.