Redirect chain checker

What this check can tell you

Trace up to five public HTTP redirects, see each response code and final destination, and detect loops or blocked redirect targets.

Limits of this result

Maximum five redirects, public standard HTTP(S) ports only. Meta refresh and JavaScript redirects are not followed. Every destination must pass network and robots-policy checks. Stopped chains show only the responses actually observed.

Common fixes to consider

• Point old URLs directly to their intended final destination to avoid unnecessary hops.
• Remove redirect loops and HTTPS-to-HTTP downgrades. Verify the chosen redirect status matches the move’s purpose.

Example result

http://example.com/old → 301
https://example.com/new → 200

An example two-response chain: the old URL redirects once, then the new page responds successfully.

Read the technical reference

Keep checking after today

A one-time result describes one response. Read our guide to ongoing monitoring to understand scheduled checks, domain ownership and confirmed changes. Explore monitoring features and plan limits.

Related checks

All tools and privacy details