Free technical website tool
Trace HTTP Status Codes and Redirect Chains
Enter one public URL to follow up to eight responses, identify 301 or 302 hops, and confirm the final destination.
URL to check
The checker follows server-side HTTP redirects.
For safety, private networks, local hosts, credentialed URLs and non-HTTP protocols are blocked. Results are briefly cached to protect the service.
Response chain
Redirect hops will appear here.
What the redirect checker shows
Each row includes the HTTP status code, requested URL and response time. The chain makes it easier to spot temporary redirects, broken destinations, loops and unnecessary multi-hop paths.
Common status codes
- 200: the requested resource returned successfully.
- 301: a permanent redirect, commonly used after a URL migration.
- 302 or 307: a temporary redirect.
- 404: the requested resource was not found.
- 500–599: the server could not complete the request.
How to use redirect results
For migrations and redesigns, aim for one direct permanent redirect from the old URL to the most relevant live destination. Test internal links separately and update them to point directly to the final URL instead of relying on the redirect.
Need help implementing the result?
Avenzo Digital builds, improves and migrates conversion-focused websites.