Trace the full redirect chain of any URL
Paste a URL. Hopcheck follows every redirect one hop at a time and shows the whole chain — each URL, the status code that caused the hop, and what finally answered. The middle is the product, not just the destination.
How it works
A link can arrive at the right page while quietly dropping its query string, downgrading from HTTPS to HTTP for one hop, or bouncing through a tracker nobody knew was there. Each of those is invisible if you only check the destination.
Paste any URL
A short link, a campaign URL, a redirect from your own site — anything that resolves over HTTP or HTTPS.
Hopcheck traces each redirect
Starting from your URL, it follows each redirect manually — one at a time — recording the status code (301, 302, 307, or 308) and the next location.
Read the full chain
Every hop is laid out in order with its URL, status, and query-string state. Dropped parameters, plaintext hops, and loops are flagged explicitly.
What Hopcheck reveals
Things you miss when you only look at where you landed.
- A lost
?ref=parameter means lost attribution for a campaign URL. - A plaintext HTTP hop in an otherwise HTTPS chain means credentials and query data were transmitted in the clear on that hop.
- A redirect loop means a page nobody can reach.
- A 301 permanent redirect when you expected a 302 temporary redirect means search engines and browsers will cache the destination permanently.
- A timeout at hop 4 means the chain broke, but not at the source — and that tells you something about where the problem lives.
Who needs Hopcheck
Marketers checking a campaign URL before it goes out — verifying every ?utm_source= survives the redirect chain.
Support staff handed a short link by a customer who will not click it. Trace it before you tell them what is on the other side.
Developers debugging a redirect configuration — verifying that 301s are 301s, that HTTPS stays HTTPS, and that nothing silently rewrites the path.