Bulk Redirect Checker
Compare saved HTTP redirect chains from up to 20 starting addresses. Review repeated targets, missing responses and recorded HTTP errors, then export a local report.
Bulk Redirect Checker: how to use it
- Enter the starting URL and paste saved response status lines and headers in capture order. Use one chain per entry and leave out response bodies.
- Add the remaining chains or load the four-chain example. Select Compare captures.
- Open the chain details to see each hop. Copy or download the comparison as JSON.
Limits and notes
Use up to 20 chains, 50,000 characters per capture and 200,000 characters in the batch. Results describe the responses you supply. The report withholds URL credentials, query values, fragments and raw headers.
How your privacy works →Bulk Redirect Checker: common questions
How are relative redirect targets resolved?
Each relative Location uses the address of its recorded response. Supply a starting URL to resolve relative targets in the first hop.
What does a repeated address mean?
A redirect target matches an earlier address in the same capture. Fragments are ignored for that comparison because they are handled by the client.
Is a saved 301 enough to report a final status?
Include the next response block to see its status. A capture ending at the 301 shows Final response unavailable.