All 14 tools / Crawlers, links and search

Follow a URL hop by hop and flag redirect chains, loops, HTTPS downgrades and dropped query strings.

Redirect tracerFreeFor site owners and developers

5 min

saved on a typical run. Our estimate, against running curl -I by hand for each hop and comparing the results.

Before: what you give it

The example input, as typed in. You give it a page address.

http://allthepossibles.com

After: what comes back

The first lines of a real run of the tool's own code on that input, fetched live when the sample was made, so the live page can differ from it. Nothing here is edited by hand.

2 hops, 241 ms, final HTTP 200
  1. 301  http://allthepossibles.com/
       to https://allthepossibles.com/  (65 ms)
  2. 200  https://allthepossibles.com/  (171 ms)

No problems found.

What you get

Every hop with status, destination and timing, then findings on what is wrong with the chain

What it cannot do

Follows up to 10 hops with an 8 second timeout each, and sees only what a plain request sees, not redirects done in JavaScript.

Who it is for

Site owners
Developers

Free and Pro

Free	20 runs a day per IP address.
Pro	No daily limit, 300 requests a minute.

Daily caps for every tool

Use it from your assistant

The tool is called trace_redirects. Connect the server once, then ask for it by name or describe the job. Install steps.

claude mcp add --transport http toolbox https://toolbox.allthepossibles.com/mcp

curl -X POST https://toolbox.allthepossibles.com/api/redirects -H 'content-type: application/json' -d '{"url":"http://allthepossibles.com"}'

Try it here

The form starts with the same example input, so you can run it first and then swap in your own.

Starting URL