Redirect Checker
See a readable final URL after browser-followed redirects. Intermediate hops and Location headers are not shown; CORS can leave the result unknown.
Your browser sends a GET request to the entered URL and follows redirects automatically. Readable responses show the final status; CORS restrictions can hide it. Individual redirect hops and response headers are not shown.
See where a readable browser request ends
Enter a URL and choose Look up. The browser follows redirects automatically. If the final response permits cross-origin access, the result shows its status and final URL when fetch reports a redirect. This is a destination check, not a step-by-step chain tracer.
For example, a starting URL may end at an HTTPS destination with HTTP 200. This tool cannot say whether the path involved one 301, several redirects or an intermediate error. It also cannot inspect Location headers or diagnose redirect loops reliably.
When the result is unknown
Many target sites do not expose their responses to another site's browser script. A blocked or opaque result is labeled Unknown; it is not proof that a redirect succeeded or failed. Check the URL in your browser's network panel or a trusted server-side tool when you need the full chain.
The entered URL is requested directly from your browser, so the destination may receive your IP address and normal request details. Avoid testing confidential links if that contact is unwanted.
Related tools: Broken Link Checker and DNS Lookup.
Frequently Asked Questions
Does this tool trace every redirect hop?
No. Browser fetch follows redirects automatically. When the final response is readable, the tool can report its final URL and status, but not each intermediate 301, 302, 307 or 308.
What does the final URL tell me?
If fetch reports a redirect, the shown final URL is the destination reached by that browser request. It does not prove the path was a single hop or that search crawlers receive the same response.
Why is the redirect result Unknown?
Cross-origin response restrictions or a blocked request can hide the final status and URL. A no-CORS fallback cannot confirm a redirect or a working destination.
How can I inspect each redirect step?
Use your browser network panel or a trusted server-side command-line tool that shows response headers without automatically hiding intermediate hops.
Where is my test URL sent?
Your browser requests the entered site directly; the destination can receive that request. ToolJiffy does not route it through a proxy.