Check where a URL redirects to and trace the full redirect chain — every 301, 302, 307, and 308 hop to the final destination. Server-side, so there are no CORS errors. Free, no signup required.
Traced server-side, so there are no CORS errors. Follows every 301, 302, 307, and 308 hop — up to 15 redirects.
A redirect checker takes any link, requests it the way a browser would, and reports every stop along the way. Where your browser silently jumps to the final page, this url redirect checker pauses at each hop and records the URL and its HTTP status code, so you can see the entire route rather than just the destination.
That matters because a single link can hide several redirects. A shortened link might pass through the shortener, an ad or affiliate network, an http → https upgrade, and a non-www → www rule before it ever reaches the real page. When you check a redirect link here, all of those hops become visible.
Use it to check redirects before clicking an unknown short link, to confirm a campaign link lands on the right page, to debug a misconfigured server rule, or to audit whether your old URLs still follow the redirect to their new homes.
Example chain
301 http://example.com
301 https://example.com
200 https://www.example.com/home
Two hops here could be collapsed into one by pointing the first URL straight at the final https://www address.
The status code on each hop tells you what kind of redirect it is. Whether you run a 301 redirect checker pass on a migrated page or debug a temporary route, knowing the difference is what keeps link equity intact.
The resource has permanently moved to a new URL. Search engines transfer almost all ranking signals (link equity) to the target and update their index over time.
When to use: Use for permanent moves: domain migrations, HTTP→HTTPS, non-www→www, or retiring an old page in favour of a new one.
The resource is temporarily at a different URL. Browsers keep requesting the original address, and search engines usually keep the original URL indexed.
When to use: Use for short-lived moves: A/B tests, geo or device routing, maintenance pages, or seasonal landing pages.
The strict HTTP/1.1 version of a temporary redirect. Unlike 302, it guarantees the request method and body are preserved (a POST stays a POST).
When to use: Use when a temporary redirect must not switch a POST into a GET — common with APIs and form submissions.
The strict permanent counterpart to 301. It passes link equity like a 301 but also preserves the HTTP method and body.
When to use: Use for permanent moves where the request method must be preserved, such as permanently relocating an API endpoint.
Rule of thumb: permanent moves → 301 or 308, and temporary moves → 302 or 307. Reach for the 307/308 pair when the request method must be preserved.
Redirect loops
A loop is when URLs redirect back to each other forever (A → B → A), which browsers report as ERR_TOO_MANY_REDIRECTS. This checker follows up to 15 hops; if a link never resolves to a final 2xx page or you see the same URLs repeat, you have a loop. They usually come from two conflicting rules — for example both a www and an HTTPS rule trying to run first.
Long chains
Every hop is a separate round trip that slows the page and can shed a little ranking value. When you check site redirects and see three or more hops, flatten them: update the first URL to point directly at the final destination so visitors and crawlers arrive in one step.
Unexpected hosts
When you check a website for redirects, watch for hops onto domains you do not recognise. A link that quietly detours through an unfamiliar host can signal cloaking, an expired shortener that has been re-registered, or a phishing hop. Confirming the final destination before you click is the safest habit.
This tool intentionally checks one URL at a time. That keeps each trace fast and readable, and keeps the free service fair for everyone. To review a batch, run your important links through the checker one after another:
For a full-site crawl of thousands of URLs, a dedicated crawler is the right tool. For spot-checking, debugging, and verifying individual links, checking them one at a time here is quick and precise.
Yes — and that is the point. Because the redirect is followed on our server rather than in your browser, you get to see the final destination without opening the link yourself. That makes this a safe way to inspect a suspicious short link from an email, DM, or social post before you decide whether to trust it.
For safety, the checker only follows public http and https addresses. It refuses to trace into private networks, localhost, or cloud-metadata endpoints, and it re-runs that check on every hop so a redirect cannot quietly send the request somewhere internal. It reads response headers to map the chain — it does not execute page scripts.
Redirects are how the web keeps old links working, so getting them right protects both users and rankings. When a page moves, a 301 passes almost all of its accumulated link equity — the ranking value from every inbound link — to the new URL. Use a temporary 302 by mistake and search engines may keep the old URL indexed and hold that value back.
Chains dilute the benefit. Each additional hop is another request before the page renders, which hurts Core Web Vitals, and every hop is a small opportunity for signals to leak or for a rule to break. Regularly running a check redirects pass on your key pages keeps chains to a single hop and confirms nothing has silently changed.
The practical takeaway: prefer one 301 straight to the final destination, avoid mixing temporary and permanent redirects on the same path, and eliminate loops. A quick trace here tells you whether your redirects are helping or quietly costing you traffic.
These three tools overlap but answer different questions. Pick the one that matches what you need to know about a link:
A redirect checker is a tool that requests a URL and reports every redirect it goes through before reaching the final page. Instead of silently following the redirects like a browser, this URL redirect checker traces the whole chain and shows you each hop, its HTTP status code (301, 302, 307, 308), and the final destination — so you can see exactly where a link leads.
Paste the link into the box above and press Check. The tool follows the redirect on the server, so there are no browser CORS errors, and returns the full path from the URL you entered to the page that finally loads. This works for short links (bit.ly, t.co, tinyurl), tracking links, affiliate links, and any normal website URL.
A checker that runs entirely in your browser has to use fetch() against the target site. Browsers block reading the response of a cross-origin request unless the site sends CORS headers — which almost no site does for a redirect — so the check fails. This tool runs the request from our server instead, which is not subject to CORS, so it can actually follow the redirect and read every hop.
A 301 is a permanent redirect: it tells browsers and search engines the page has moved for good and passes almost all of its ranking value (link equity) to the new URL. A 302 (and 307) is a temporary redirect: the original URL stays indexed and search engines expect the page to come back. Using a 302 when you meant a 301 is a common SEO mistake because link equity may not transfer.
A redirect chain is when a URL redirects to another URL, which redirects again, and so on — for example http → https → non-www → final page. Every extra hop adds a round trip that slows the page down, can leak a little link equity, and increases the chance something breaks. Tracing the redirect chain lets you flatten it: point the first URL straight at the final destination wherever possible.
A redirect loop happens when URLs redirect back to each other endlessly (A → B → A). This checker follows up to 15 hops; if a link keeps redirecting without ever returning a final 2xx response, or you see the same URLs repeat in the chain, you almost certainly have a loop. Browsers show this as 'ERR_TOO_MANY_REDIRECTS'. Fix it by making sure exactly one rule matches each URL.
This tool checks one URL at a time so results stay fast and readable and to keep the service fair for everyone. To check a site's redirects in bulk, run your key URLs through one at a time — homepage, top landing pages, and any old URLs you have 301'd — and confirm each lands where it should. For large-scale audits, a crawler is the right tool; this checker is ideal for spot-checking and debugging individual links.
A single, correct 301 redirect is perfectly SEO-friendly and is the recommended way to move a page. Problems come from long chains (301 → 302 → 301 → 200), redirect loops, temporary redirects used for permanent moves, and redirects that change the destination unexpectedly. Keeping chains to one hop and using the right status code preserves link equity and page speed.
This tool follows HTTP-level redirects (the 3xx status codes with a Location header), which is how the vast majority of redirects work. Meta-refresh and JavaScript redirects happen after the HTML loads, so they may not appear in the HTTP chain. If a link resolves to a 200 page but still bounces you elsewhere in the browser, a client-side redirect is the likely cause.
Yes. This is a free, browser-based utility with no signup and no account required — paste a URL and check its redirects. If you later want to create your own short links and see real-time click analytics, you can do that with a free Track Link account, but it is not needed to use this checker.
Create tracked short links with full click analytics. See who clicks, from where, and what they do — in real time.
Start tracking free