Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Redirect Detective?
Redirect Detective is a free URL redirection checker that displays the full chain of hops a link passes through before landing on its final destination. Instead of showing only the endpoint, it exposes each intermediate redirect, which helps you see what happens between the link you click and the page you reach.
What it is useful for
- Uncovering affiliate links: see where a shortened or cloaked affiliate link actually leads and which affiliate network is involved.
- Vetting shortened URLs: check whether a bit.ly-style link resolves to a legitimate site or something unexpected.
- Auditing your own redirects: confirm that redirects work correctly, including domain migrations where an old domain should forward to a new one.
- Spotting tracking and cookies: identify at which point in the chain cookies are set, and recognize adware or tracking redirects you may want to avoid.
- Counting hops: some sites chain many redirects, and the tool makes that count visible.
Who benefits
SEO specialists and webmasters auditing link equity and redirect hygiene, affiliate marketers verifying link destinations, security-conscious users checking unfamiliar short links, and anyone curious about where a link really goes.
A practical next step
Paste a suspicious short link or one of your own redirecting URLs into the checker and read the chain top to bottom. If you see unexpected third-party domains or cookie-setting hops, treat that as a signal to investigate further before clicking or sharing the link.
How can I use Redirect Detective to reveal where an affiliate link sends users and which affiliate network it uses?
Paste the affiliate link into Redirect Detective's URL field and run the check. The tool displays the redirect chain in full, so you can follow each hop from the original link to the final destination page. That chain is the core of the answer: the affiliate network usually appears as an intermediate domain in the path, and the final landing page shows where the visitor actually ends up.
What to look for in the chain
- The network hop. Intermediate domains often belong to an affiliate or tracking network, and the URL on that hop frequently carries parameters identifying the program, offer or click ID. Read the hostname and query string at each step.
- The final destination. The last URL is the page the visitor sees. Compare it with what the link promised.
- Cookie-setting points. The page notes you can see where cookies are set along the path, which helps you judge how much tracking happens before the landing page.
- Chain length. The page points out that some well-known sites use many redirects, so a long chain is not automatically suspicious, but every extra hop is another party involved.
A practical example
A reader receives a shortened link in a message. Running it through Redirect Detective may show a shortener domain, then a network domain with tracking parameters, then the merchant's product page. The middle hop tells them which network is being used; the last hop tells them whether the offer is genuine. If the chain ends somewhere unrelated to the message's claim, that is a concrete warning sign.
Decision criteria
Use the tool when you need evidence rather than a verdict. It shows the path; judging legitimacy still depends on whether the final site is one you trust and whether the intermediate domains match a known network. For links you plan to click, checking first also lets you avoid being routed through adware or tracking sites, which the page lists as one of its uses.
For background on how redirects and affiliate tracking work, Redirect Detective also links to its own FAQ and redirect resources pages, which are a sensible next stop after your first chain.
How do I check whether a shortened URL like bit.ly leads to a legitimate site before clicking it?
You can't fully verify a bit.ly link before clicking it, but you can trace where it redirects without loading the destination page in your browser. Redirect Detective is built for exactly this: its page describes a free URL redirection checker that "display[s] redirects in full," showing the complete path a redirected URL passes through rather than just the final destination.
What to look for in the redirect chain
- The final domain. A short link to
bit.ly/xyzmay land on a lookalike domain (e.g., a misspelled bank name) rather than the real site. Judge legitimacy by the final hostname, not the shortener. - Intermediate hops. Chains that pass through adware or tracking domains before reaching the destination are a warning sign, especially for links arriving unsolicited.
- Where cookies get set. The page notes you can "see at what point in the redirection path cookies are being set" — unexpected cookie-setting hops suggest tracking.
- Length of the chain. Many redirects aren't automatically malicious, but a long chain through unfamiliar domains deserves more caution than a single hop to a known site.
A practical routine
- Paste the short URL into a redirect checker and read the full chain.
- Confirm the final domain matches what the sender claims (a bank, a store, a document host).
- If the chain runs through unknown tracking or adware domains, don't click — reach the destination by typing the official address yourself.
- For links claiming to be from a company, verify through its official site or app rather than the link itself.
Honest trade-offs
A checker shows you the path, but it can't tell you whether the final page hosts malware or a convincing phishing form. Treat a clean chain as a necessary check, not a guarantee. Also note that some shorteners and redirectors behave differently for automated requests than for a real browser, so a checker's result may not match exactly what you'd see.
A concrete case: a text message says "your parcel is held, reschedule here" with a bit.ly link. Tracing it might reveal a hop through an unfamiliar domain ending at a lookalike courier site — enough to delete the message and visit the courier's official site directly.
How can I test my own redirects to confirm they work correctly and that my old domain properly forwards to the new one?
Use a redirect checker that displays every hop in the chain, not just the final destination. On Redirect Detective, that is the core function: you enter a URL and see the complete path it follows, including intermediate redirects. That matters for your case because "old domain forwards to new domain" can fail in ways a browser hides—an extra hop, a loop, a redirect to http instead of https, or a chain that stops on a parked page.
Redirect Detective
A practical test sequence
- Test the bare old domain (
olddomain.com) and thewwwversion separately. They often behave differently. - Test a few deep links, not just the homepage—e.g.
olddomain.com/pricingand a blog post. Confirm each maps to the equivalent page on the new domain, not all to the homepage. - Check the status codes. A permanent move should use 301 (or 308); a temporary one uses 302/307. Mixing these up affects search engines and browser caching.
- Look for chains. Old domain → new domain → trailing-slash fix →
httpsis three hops; collapsing them to one is faster and easier to maintain. - Watch for loops (A → B → A) and for redirects that land on a 404.
- Repeat after any server or DNS change, and test from a clean session so cached redirects don't mask problems.
What to look for in the results
| Symptom in the chain | Likely cause | What to do |
|---|---|---|
| Ends on a 404 or parked page | Wrong target path or expired hosting | Fix the destination rule in your server or DNS config |
Redirects to http:// |
Missing HTTPS rule | Add an HTTPS redirect ahead of the domain move |
| Several hops | Layered rules (www, HTTPS, domain move) | Consolidate into one rule per case |
| All paths go to homepage | Catch-all redirect | Add path-preserving rules for key URLs |
| Loop | Conflicting rules | Remove the rule pointing back to the source |
Beyond your own site
The same tool is useful for auditing links you publish or receive: shortened links, affiliate links, and outbound links that may pass through tracking domains. If you want a second opinion or a bulk check, HTTP Status shows status codes and chains for multiple URLs at once, and Ahrefs includes a redirect report in its site audit for finding broken or chained redirects across a whole site.
Decision criterion
For a small site, manual spot checks of the homepage, www, and your ten most-linked pages are usually enough. For a site with hundreds of moved URLs, run a crawler-based audit once, fix chains and 404s, then spot-check monthly—redirects tend to break quietly after CMS or hosting changes.
How can Redirect Detective help me identify where in a redirect chain cookies are set so I can avoid adware or tracking sites?
Redirect Detective shows the full path of a redirect chain and flags the point at which cookies are set, so you can see which hop in the chain drops them—often an intermediate ad or tracking domain rather than the destination site you intended to reach. According to the site's own description, it is a free URL redirection checker that displays redirects in full and lets you "see at what point in the redirection path cookies are being set," with avoiding adware/tracking sites listed as one of its stated uses. Redirect Detective
How to use it for this purpose
- Paste the link you are about to click (a shortened link, affiliate link or a redirecting URL from an email or ad) into the checker.
- Read the hop-by-hop list. Note every domain you don't recognize, especially ones that look like ad exchanges, click trackers or URL shorteners.
- Look at where the cookie-setting step appears. If a cookie is set before you reach the final site, the domain setting it is the one doing the tracking—that is your signal to stop and avoid the link.
- Decide based on the destination: if the chain ends at the site you actually want, try to reach it directly (typing the address or using a bookmark) so you skip the tracked hops entirely. If the chain ends somewhere unexpected, treat the link as untrustworthy.
Practical limits
The tool tells you what happens on the path it observes; it does not block tracking for you, and cookie behavior can vary by browser, region or visit, so a clean result on one check isn't a guarantee. For everyday protection, pair this kind of spot-check with browser privacy settings or an extension that blocks known trackers—the checker is best used as a diagnostic before you click something suspicious, not as ongoing protection.
A concrete case: a shortened link in a message claims to point to a document. The checker shows it passing through two unfamiliar domains, one of which sets a cookie before landing on a file-sharing page. You skip the link and ask the sender for the direct address instead.
Can Redirect Detective show me the full redirect path for well-known sites such as gmail.com, facebook.com, or office365.com?
Yes. Redirect Detective is built to display a redirect chain in full, so you can trace every hop from the URL you enter to its final destination. The site specifically names gmail.com, facebook.com and office365.com as examples of well-known sites that use redirects, which suggests these are the kinds of multi-hop paths the tool is meant to handle.
What the full path shows you
- Each hop in order, so you can see intermediate domains rather than just the start and end.
- Where cookies get set along the way, which matters if you care about tracking.
- The final destination, useful for checking whether a shortened or affiliate link lands somewhere legitimate.
- Whether your own redirects work, including a domain move to a new address.
A practical scenario
Say a colleague sends you a shortened link. Pasting it into Redirect Detective lets you see the intermediate sites before you commit to opening it. Similarly, if you run a site and have just migrated domains, you can confirm the old address redirects cleanly to the new one without stray hops.
Decision criterion
Use it when the route matters—affiliate links, shorteners, tracking parameters, domain migrations. If you only need the final URL and not the path, a simpler check may be enough. For related reference material, the site also links to redirect resources and an FAQ from its homepage at Redirect Detective.
User reviews (0)