Link Checker
What is a URL redirect checker?
Have you ever wondered: where does this link go? A redirect checker follows the path of a URL. It shows the full redirection path of normal links, shortened links, and tiny URLs, one hop at a time, right up to the final destination. Tools like this are also called link checkers, URL checkers, redirect tracers, link followers, and 301 redirect checkers.
The tracer records every link in the chain, including PHP redirects, htaccess redirects, NGINX redirects, meta refreshes, and simple JavaScript redirects. Nothing is followed blindly: each response is captured with its status code and headers before the next hop is requested.
Why use a redirect link checker?
Redirect tracing turns a black box into a readable chain. That is useful for troubleshooting, competitive research, and affiliate work, and it is how you catch a broken hop before a visitor does.
Troubleshooting redirect problems
When you migrate a site or rename a URL you forward the old address to a new one. A single wrong hop can send visitors to a 404, and an error anywhere in a chain stops everyone behind it. Trace the address first, then fix the hop that breaks.
SEO redirect chains
Search engines follow links, so a chain is crawled as a chain. Every extra hop is another place for the chain to break and another chance to lose link equity. Keeping redirects direct is one of the cheapest SEO wins available.
Affiliate link tracking
Short links and tiny URLs hide the destination until you click. If one hop in an affiliate chain breaks, the commission is gone. Trace your links on a schedule and confirm the final landing page is the one you were promised.
Tiny URL expander
Paste any short link and read the real address before you open it. The chain shows which networks, trackers, and affiliate programs sit between the link and the destination.
Cut out middlemen
The hop immediately before the destination is usually the real affiliate program. Everything before it is taking a cut. Trace your existing programs, then apply to the source directly.
How this tracer works
Requests run server-side with the platform's automatic redirect handling switched off. Each 3xx response is recorded with its status line and headers, its Location is resolved against the current URL, and cookies set along the way are forwarded, exactly as a browser would do it. The chain stops at the first non-redirect response, at the hop limit, or when a loop is detected.
The tool is honest about its limits: it is a bot, so its user agent is visible to the server, and it cannot execute JavaScript the way a browser can. Delayed or scripted bounces are detected only when the URL appears literally in the first 96 KB of HTML.
Frequently asked questions
Is tracing a link safe?
Mostly. A trace performs a GET request, so the destination sees a visit from the server. It does not run scripts, download large files, or sign you in. It also does not judge whether content is malicious.
Why did I get a 403?
Many sites block bots. Switch the user agent to a normal browser, add the referer you would really arrive with, and trace again. If the block persists, the site inspects TLS or JavaScript beyond what a plain request can satisfy.
What is the longest chain it will follow?
Fifteen hops by default and twenty at most, with a 45 second total budget and a 15 second limit per hop. Chains longer than that are rare and almost always broken.
Does it work with POST-only links?
Partially. The tracer sends GET or HEAD. Links that require a form submission redirect differently, and 303/307/308 semantics are reported but not simulated with a body.
Using the tracer from code
A JSON endpoint backs the form, so the same work can run from a shell:
curl -s http://127.0.0.1:8787/api/trace \
-H 'content-type: application/json' \
-d '{"url":"https://example.com/some/redirect"}'
Every trace returns a permalink under /trace/<id>/ plus a JSON copy at /trace/<id>.json. Results live for seven days.