Redirect Checker
Trace the full redirect chain for any URL — see each hop, status code, and the final destination.
Did this tool work for you?
How to use this calculator
- 1
Enter the URL you want to trace (including http:// or https://).
- 2
Click "Check Now" to follow all redirects step by step.
- 3
Each row in the chain shows the URL, HTTP status code, and where it redirects.
- 4
The final row shows the destination with its status code.
Frequently asked questions
How does the tool trace a redirect?
Our server sends a HEAD request to the URL without following redirects, records the status code and Location header, then repeats the request against the Location address until it reaches a response that is not a redirect, has no Location header, repeats an address it has already requested, or has followed 15 redirects. Relative Location values are resolved against the current URL. If a HEAD request fails or is rejected with 405 or 501, it retries that hop with GET. Every hop must be a public internet address.
How is the Redirects count worked out?
It is the number of redirect responses followed, so a URL with no redirect shows 0 and a URL that redirects once shows 1. The table lists every request including the final page, which is one more row than the count. The count is green up to 2 and amber above that.
How is the Redirect type line decided?
It looks at every redirect status in the chain. If all are 301 or 308 it reports Permanent, if all are 302, 303 or 307 it reports Temporary, and if the chain mixes both it reports Mixed permanent and temporary. The status codes seen are listed in brackets, and a chain with no redirect reads No redirect.
What is the difference between 301, 302, 307 and 308?
301 and 308 are permanent; 302 and 307 are temporary. The pairs differ in method handling: 307 and 308 require the client to repeat the same method and body, while with 301 and 302 browsers historically changed POST to GET. Search engines treat the permanent codes as a signal to move to the new address. Use 301 or 308 for a lasting move and 302 or 307 for short-term changes.
Will it detect meta refresh or JavaScript redirects?
No. It follows only HTTP redirects signalled by a status code in the 300 range and a Location header. A page that sends users on with a meta refresh tag or with script returns 200 here and shows as no redirect. Those need a browser-based check.
Why does entering example.com not show the http to https redirect?
When the address has no scheme the tool adds https://, so it begins at the secure version. To test the upgrade from plain http, enter the address with http:// at the start. Test the www and non-www versions separately, too.
How does it handle redirect loops?
It stops as soon as a redirect points back to an address that was already requested and shows a Problem line naming it, so a loop is reported rather than left for you to spot. A chain that is simply very long stops after 15 redirects with a message. Each request has an 8-second timeout, and a request that fails outright ends the check with an error.
Can I trace a redirect on localhost or an internal address?
No. The tool runs on our server, so it only follows public internet addresses. Localhost, private network ranges and similar reserved addresses are refused, and so is a public URL that redirects into one of them: the check ends with an error before that request is made. To test a staging site, put it on a public address or run a command such as curl -I -L from your own machine.
Tracing HTTP redirect chains hop by hop
What the output contains
The result is a table with one row per request: the URL requested, the status code returned, and the Location header, if any. Below it, a summary lists the number of redirects, the final URL, the final status and a redirect type. The tool does not follow redirects automatically; it reads each response itself, so you see every intermediate address. Chains arise when several rules stack up, for instance one rule that forces HTTPS, another that adds www, and a third that appends a trailing slash. Each extra hop is one more round trip before the visitor or crawler reaches content.
Status codes you will meet
The status column decides what the redirect means. The tool’s summary does not separate them all, so use this reference.
| Code | Meaning | Permanent? | Method kept? |
|---|---|---|---|
| 301 | Moved Permanently | Yes | Not guaranteed; POST may become GET |
| 302 | Found | No | Not guaranteed; POST may become GET |
| 303 | See Other | No | Client switches to GET |
| 307 | Temporary Redirect | No | Yes |
| 308 | Permanent Redirect | Yes | Yes |
Example inputs and what a healthy result looks like
Test the four common entry points of a site separately: http://example.com, http://www.example.com, https://example.com and https://www.example.com. A well-configured site sends the three non-canonical versions directly to the canonical one in a single redirect, using a permanent code, and the canonical address itself returns 200 with no redirect. Warning signs in the table are a chain of three or more requests, a temporary code on a move that is meant to be permanent, a redirect that lands on a 404, a redirect to the home page instead of the matching new page after a site move, and an address that ends in a loop. If you migrate, check a sample of old URLs and confirm that each ends on its true equivalent.
What the checker cannot see
It reads only server-side HTTP redirects, so meta refresh tags and JavaScript redirects are invisible to it. It sends a plain request without cookies, so redirects that depend on login, country, language headers or device type may differ for real visitors. The request comes from our server and uses HEAD first, and some servers answer HEAD differently from GET. Use the result to find chains and wrong status codes, then fix them where the rules live: the web server configuration, the CDN, the application or the hosting panel.
Learn more from an authoritative source:
MDN Web DocsTTFB Checker
Measure Time to First Byte (TTFB) for any URL — see how fast your server responds and identify bottlenecks.
Website Page Size Checker
Check the HTML page size of any URL and get a resource breakdown — images, scripts, stylesheets, and inline assets.
Website Screenshot Tool
Capture a full-page screenshot of any website URL without installing any software.
.htaccess Generator
Generate an Apache .htaccess file with HTTPS redirects, www rules, caching headers, and custom error pages.
JSON Formatter & Validator
Format, validate, and minify JSON — with clear error messages for invalid input.
Base64 Encoder / Decoder
Encode plain text to Base64 or decode Base64 strings back to readable text.
Results are estimates for informational purposes only and do not constitute professional financial, medical, legal, or technical advice. Read full disclaimer →