Redirect Checker

Server assisted Web

Follow up to 10 redirects from any public URL and inspect status codes, Location headers, HTTPS upgrades, loops and total latency — essential for SEO migrations and link checks.

Privacy: This tool sends the request through the Mutqan backend relay to reach the target. Only the target URL, headers and body you enter are transmitted, and nothing is stored.

How to use Redirect Checker

  1. Enter the URL to trace — start with http:// to check the HTTPS upgrade too.
  2. Optionally lower the maximum number of hops.
  3. Run the trace and inspect each hop; the Findings list suggests fixes.

Redirect Checker features

  • Follows up to 10 hops and lists URL, status, meaning, Location header and time per hop
  • Summary of redirect count, final status, final URL, total latency and HTTPS state
  • Loop detection and warnings for long chains, temporary redirects used for permanent moves, relative Location headers and HTTPS downgrades
  • Highlights host changes across the chain (http → https → www)
  • CSV export of the chain for SEO migration audits

Redirect Checker example

Trace an old blog URL

Input:

http://example.com/blog/post

Output:

1  http://example.com/blog/post      301 → https://example.com/blog/post   38 ms
2  https://example.com/blog/post     301 → https://www.example.com/blog/post   41 ms
3  https://www.example.com/blog/post 200                                       120 ms
Findings: Long chain (2 redirects) — point the original URL straight at the final one · HTTPS upgrade at hop 2.

Frequently asked questions about Redirect Checker

How many redirects are acceptable?

Ideally one. Every hop costs a round trip and search engines pass slightly less ranking signal through long chains. The tool warns when a chain has more than two redirects or crosses several hosts.

What is a redirect loop?

A chain that returns to a URL it has already visited (A → B → A). Browsers give up with ERR_TOO_MANY_REDIRECTS. The relay detects loops and stops early.

Why start with http:// instead of https://?

Starting from plain HTTP shows whether the site upgrades to HTTPS, with which status code, and whether the www/non-www canonicalisation happens in the same hop or adds another redirect.

Why do results differ from what I see in my browser?

The relay sends a generic request without your cookies, language or device headers. Sites that redirect based on login state, geolocation or User-Agent may behave differently.

Technical notes

Redirects are followed by the Mutqan relay without cookies or browser headers; 301/302/303/307/308 are all followed and the method downgrade rules are noted but not applied because only GET requests are traced.