Trace the full path
Review each HTTP response, its status, Location header and time measured by your tracing endpoint. Relative locations are resolved to absolute addresses.
↗ NETWORK DIAGNOSTICS
URL Redirect Analyzer
See the complete journey from a starting URL to its final destination. Inspect every status code, discover redirect loops, and compare canonical URLs with confidence.
✓ Step-by-step chains✓ Canonical audits✓ Batch analysis
Redirect workspace
Enter URLs, connect a tracing service, then inspect the route.
ANALYSIS RESULTS
Redirect analysis
Inspected URLs
Request journey
Destination summary
UNDERSTAND EVERY HOP
A clearer way to debug redirects
Designed for site migrations, SEO checks, domain changes and troubleshooting unexpected destinations.
Find redirect problems
Detect loops, excessive hops, missing destinations, insecure HTTPS downgrades and broken final pages before they affect visitors.
Compare canonical hints
Inspect the final URL alongside HTTP Link and HTML canonical declarations, title, headers and Refresh hints. Canonicals are not HTTP redirects.
FAQ
Answers before you analyze
Understand the limits and behavior of network-level tracing.
Can this detect all kinds of redirects?
The endpoint follows HTTP 301, 302, 303, 307 and 308 Location responses. It reports Refresh hints but does not execute JavaScript, browser navigation, cookies or login flows. HSTS upgrades performed by your browser may differ.
Why can’t a static web page trace every URL directly?
The Fetch API filters cross-origin redirect responses and hides intermediate status and Location information. A server-side endpoint can request the hops separately. The page remains static, but live tracing depends on that service.
What does a canonical mismatch mean?
A canonical URL suggests the preferred indexed version of a page; it does not redirect visitors. A mismatch may be intentional. Inspect your site’s canonical strategy rather than treating all differences as errors.
Is this private and accurate?
Example mode uses no network. Live mode shares submitted URLs with your chosen tracing service. Timings reflect its location and its GET or HEAD request, not your browser. Protected pages, geolocation, bot controls and cookies can change outcomes.