Network · Made a little simpler

HTTP Redirect Chain Checker

Trace redirect statuses and Location fields in saved headers. Resolve relative paths and identify repeated addresses or a missing final response locally.

Free to useNo account neededProcessed on your device
Your workspaceProcessed on your device

Add this tool to your website

Paste this code into your page to add the tool and a visible ToolMellow credit link.

HTML embed code
Preview embed

HTTP Redirect Chain Checker: how to use it

  1. Paste the saved response blocks in the order the client received them.
  2. Enter the original HTTP or HTTPS address to resolve relative Location values.
  3. Read redirect chain and check where the capture ends. Download the report if needed.

Limits and notes

Paste HTTP/1.0, HTTP/1.1, HTTP/2 or HTTP/3 status lines followed by one field per line. Each capture supports 100 response blocks, 5,000 fields and one million characters. The starting address is supplied by you. Later addresses are inferred from Location. A repeated address may be intentional. Missing responses and ambiguous targets stay visible.

How your privacy works →

HTTP Redirect Chain Checker: common questions

Can it resolve a relative Location?

A relative reference needs a known base. Enter the starting URL, or use a capture whose earlier redirect supplies an absolute address.

What if the last response has a redirect status?

The report identifies the recorded target and marks the next response unavailable. It makes no request to that address.

Guides