benchlight.

Ship & Quality · LOCAL TOOL

Redirect Chain Inspector

Trace exact local-path rules written as /source -> /destination. Report each source's full chain, terminal destination, hop count, and cycle status.

Runs in this page
No API call
WORKSPACEINPUT → RESULT
01

Your input

LOCAL
Redirect Chain Inspector inputs
02

Result

Run the tool to see a result.

Your result will appear here. Input is not saved.

Browser-side processingNothing is sent to a tool API.

WHY THIS TOOL EXISTS

A focused job, not a black box.

The tool traces the supplied graph without visiting any destination. Duplicate sources stay visible, with first-rule-wins behavior stated explicitly instead of silently overwriting a rule.

How to use it

  1. Translate exact path rules into the displayed arrow format.
  2. Run the chain inspection.
  3. Resolve cycles and duplicate sources, then review unnecessary extra hops.

TRY A WORKING EXAMPLE

Start with known input.

Load this sample into the workspace, run the tool, and compare the result shown below.

Show sample input
{
  "rules": "/old -> /guide\n/guide -> /docs\n/loop-a -> /loop-b\n/loop-b -> /loop-a"
}

Expected sample result from the local tool

2 cyclic source(s) · 0 duplicate rule(s).

{
  "chains": [
    {
      "source": "/old",
      "path": [
        "/old",
        "/guide",
        "/docs"
      ],
      "hops": 2,
      "cycle": false,
      "destination": "/docs"
    },
    {
      "source": "/guide",
      "path": [
        "/guide",
        "/docs"
      ],
      "hops": 1,
      "cycle": false,
      "destination": "/docs"
    },
    {
      "source": "/loop-a",
      "path": [
        "/loop-a",
        "/loop-b",
        "/loop-a"
      ],
      "hops": 2,
      "cycle": true,
      "destination": null
    },
    {
      "source": "/loop-b",
      "path": [
        "/loop-b",
        "/loop-a",
        "/loop-b"
      ],
      "hops": 2,
      "cycle": true,
      "destination": null
    }
  ],
  "duplicates": []
}

First rule wins for repeated sources. Exact paths only; no regex, wildcards, status codes, or network checks.

LIMITS AND INTERPRETATION

What the result cannot tell you.

Up to 1000 literal rules. The first occurrence of a source wins. Regex, wildcard substitution, query matching, redirect status, and live HTTP behavior require separate checks.

Inputs are processed in this page and are not written to local storage.