Redirect chain inspector

Follow each redirect, one hop at a time.

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. It does not follow the chain silently and report the destination — the middle is the product.

Check a link See pricing

What the middle can change

A link can arrive at the right page having quietly changed along the way.

Each of these is invisible if you only look at where you landed — and each one breaks something real.

Query lost

A dropped query string

A link can arrive at the right page having quietly lost its ?ref=. A lost parameter is a lost attribution, a lost campaign tag, a broken deep link. Hopcheck shows the query string at every hop and says explicitly when one is dropped or rewritten.

Plaintext hop

One hop over HTTP

A chain that ends on HTTPS can still pass through a plain http:// hop, and that one hop carries the whole URL — query string included — in clear text. Hopcheck flags any plaintext hop, even inside an otherwise secure chain.

Loop

A redirect loop

The same URL visited twice is a page nobody can reach. Hopcheck detects the loop and reports it as the distinct result it is — not as a chain that simply stopped.

Status code

The status code itself

301, 302, 307 and 308 are not interchangeable. A permanent redirect is a different fact from a temporary one. Every hop records the status that caused it and whether it is permanent.

How it works

Three steps, nothing else.

No account, no history, no scheduled re-checks. The tool answers when you ask.

Paste a URL

Any http:// or https:// link — a short link you don't trust, a campaign URL about to go out.

Each hop is followed manually

Hopcheck requests each URL with redirects turned off, reads the status and Location, then moves to the next — capped at 10 hops, and it says so when the cap is hit.

Read the evidence

The chain renders as a stack of inspection results: status code, URL, query string, and every change flagged where it happened.

Example output hopcheck /app

Hop 1 301 Permanent

https://example.com/offer?ref=summer

Query ?ref=summer — intact → Location: https://example.com/landing?ref=summer

Hop 2 200 Chain ends

https://example.com/landing?ref=summer

Query ?ref=summer — intact

If the query string had been dropped, Hopcheck would flag that hop in amber — QUERY DROPPED — and if a hop were plain http://, it would flag it in red.

Limits, stated plainly

What this tool checks — and what it will not do.

The honest boundary of the checker

Checks only the URL you type. It never crawls the destination, never follows links found on the final page, never scans a domain.
Stops at 10 hops and says so. A chain that hit the limit and a chain that ended are different results and render differently.
If a hop times out or the host will not resolve, the check says it did not complete, and at which hop. That is a failed check — not a finding about your link.
No email, no alerts, no scheduled re-checks, no saved history. There is no sender and no storage in this fleet. The tool answers when you ask.
Only HTTP 3xx redirects are followed. HTML <meta> refresh pages are reported as the final hop.

Inspect your next link before you send it.

Open the checker and paste the URL. You will see every hop, every status code, and every thing that changed along the way.

Open the checker Pricing