How to use it
- 1
Prepare source,target,status CSV or TSV.
- 2
Run the bounded check against public HTTP/HTTPS sources.
- 3
Fix mismatches, conflicts, chains, and cycles before deployment.
What the tool can do
- Compares the observed first redirect target and optional 301/302/303/307/308 status.
- Finds duplicate or conflicting sources, self redirects, map chains, and cycles.
- Revalidates DNS and every redirect target through SafeHttpFetcher.
Common use cases
- Validate a migration redirect spreadsheet after release.
- Find chains and conflicting rules before importing into nginx, a CDN, or a CMS.
- Recheck critical URLs after routing changes.
How it works inside
Each source is checked with a separate bounded safe fetch without reading the body.
The first hop is compared; additional hops are reported as a chain review signal.
Questions and answers
Can I upload a redirect map with tens of thousands of URLs?
No. This public tool is limited to 25 explicit rows. Bulk validation needs separate job architecture, queues, and rate limits.
Why compare the first redirect hop?
A redirect map usually describes the immediate source-to-target rule. The final URL is shown separately and extra hops are flagged as a chain.
