What the redirect tracer tells you
Between a link and the page it opens there can be a surprising number of steps: from plain HTTP to HTTPS, from the bare domain to www, through a link shortener, a tracking service and a language selector. Each step is a redirect, and each one can be slow, wrong or a security problem. The redirect tracer opens the address for you and shows every hop in order, so you can see exactly where a link goes and how it gets there.
What we check
For the address you enter, which can be a full URL, a short link or a bare domain, we follow the chain one hop at a time, up to 15 hops. For each hop we show:
- the status code in words, such as "301 Moved permanently" or "302 Found (temporary)";
- the address, and the server address we connected to;
- how the hop sends visitors on: an HTTP redirect, a meta refresh in the page, or a JavaScript location line we read but never run;
- the names of any cookies it sets (never their values);
- how long it took.
We then look at the chain as a whole. We flag loops, chains longer than three redirects, any step from HTTPS back to plain HTTP, temporary redirects used for what looks like a permanent move, and chains that end on an error page. We note when the chain ends on another site, when it passes through a known link shortener, and when the final address carries tracking parameters.
Copy the clean address
If the final address carries tracking parameters such as utm_source, gclid or fbclid, we show it
without them and offer a "Copy clean URL" button. The clean address opens the same page without telling
anyone where you found the link. We remove only parameters on our published list of names that do nothing
but tracking, so the page itself keeps working.
Reading the result
The timeline lists each hop with its number, status and address. The last hop is the page the chain ended on, with a tick for a successful answer and a warning for an error status. Below the timeline you'll find the total number of redirects and time, why the chain stopped if it didn't reach a page, the final page as a link, and the clean address when there is one. Findings explain anything worth changing.
When a hop points somewhere we refuse to connect to, such as a private network address or an unusual port, we stop there and show the chain so far; that's a result, not an error. If the very first address can't be fetched, the check returns an error and you aren't charged.
How we fetch
We fetch as DNSSuperBot, from our own servers, and every hop is checked against our safety rules before we connect, exactly like the first one. We never send cookies from one hop to the next and never run scripts, which is also why the result shows what a search engine or a link preview sees. We go easy on every site with a shared limit per host across all our users.
When to use it
Use it before you share or click an unfamiliar short link, after moving a site to a new domain or to HTTPS, when a page is slow to start loading, or when search engines report redirect errors. The security headers check traces all four ways into a home page at once and grades the headers on the final page, so the two tools work well together. For a whole site, the broken link checker follows every internal link and reports redirects that end on errors.