Trace every redirect hop in full detail
Most tools only show the final destination. We reveal every hop — status codes, response times, server IPs, TLS certificates, and complete response headers.
How it works
Enter a URL
Paste the URL you want to inspect into the input field above. Both HTTP and HTTPS are supported.
Run the check
The tool automatically follows every redirect and records detailed information at each step.
Review results
The full redirect chain is displayed as a timeline, with status codes, IPs, response times, and more.
HTTP Redirect Status Code Reference
Moved Permanently
The resource has permanently moved to a new URL. Search engines transfer link equity to the new address. The go-to choice for SEO-friendly redirects.
Found (Temporary)
The resource has temporarily moved. Search engines keep the original URL indexed. Ideal for maintenance pages, A/B tests, and short-term redirects.
See Other
Instructs the client to fetch the target using GET, regardless of the original method. Commonly used after a POST to prevent form resubmission.
Temporary Redirect
Similar to 302, but strictly preserves the original request method. A POST request stays POST after the redirect.
Permanent Redirect
Like 301, but strictly preserves the request method. The modern, method-safe alternative to 301.
Meta Refresh
A client-side redirect via an HTML meta tag. Not recommended for SEO, but still encountered in legacy systems and certain CMS platforms.
Frequently Asked Questions
What's the difference between a 301 and a 302 redirect?
A 301 is a permanent redirect — it tells search engines the original URL has moved for good, and link equity transfers to the new address. A 302 is temporary; search engines keep the original URL indexed. Use 301 for permanent moves and 302 for short-term situations like maintenance or A/B tests.
How does a long redirect chain affect my site?
Each additional hop adds latency and degrades the user experience. Search engines typically follow a limited number of redirects — Google caps it at around 10. Keep your chains to 3 hops or fewer, and ideally redirect directly from the original URL to the final destination.
Why is my site stuck in a redirect loop?
Redirect loops (A→B→A) are almost always a configuration error. Common culprits include conflicting HTTPS settings between a CDN and the origin server, incorrect WordPress siteurl settings, or overlapping Nginx/Apache rewrite rules.
Which status code should I use for HTTP-to-HTTPS redirects?
Use 301. It signals to search engines that your site has permanently switched to HTTPS, which is good for SEO. You can also use 308 if you need to preserve the request method, though for standard GET requests the behavior is identical.
What redirect types does this tool detect?
All standard HTTP redirects: 301, 302, 303, 307, and 308. The tool also detects client-side redirects via HTML meta refresh tags and JavaScript. The full chain is traced from start to finish.
What is the TLS information in the results useful for?
The TLS details let you verify that SSL certificates are correctly configured, check expiry dates, and confirm the issuing authority. This is especially helpful when diagnosing HTTPS-related redirect issues or mixed-content warnings.
Why do my results differ from what I see in the browser?
Browsers cache 301 redirects, so they may skip the original request entirely on repeat visits. This tool always makes a fresh request with no cache, giving you the real-time server response. Try clearing your browser cache and comparing again.
Is this tool free? Are there any usage limits?
Completely free, no account required. To prevent abuse, each IP address is limited to 5 requests per 10 seconds — more than enough for normal use.