HTTP Status & Redirect Checker

Trace the HTTP status code and full redirect chain step by step.

The HTTP Status & Redirect Checker shows every step a URL takes before reaching its final destination. For each hop it lists the HTTP status code (301, 302, 307, 308, and so on) and the address it moved to, so you can see the intermediate path your browser never reveals on screen.

It is handy for diagnosing misconfigured permanent redirects, forced http→https upgrades, www canonicalization, redirect loops, and the long redirect chains that hurt SEO. Just enter a URL and the server safely makes the request on your behalf, returning the exact status codes and the path it followed. Results are briefly cached for speed.

URLe.g. https://example.com (enter the full URL)

Status codes at a glance

2xx: Success. 200 OK is a normal final response.
3xx: Redirect. 301 and 308 are permanent; 302 and 307 are temporary.
4xx: Client error, such as 404 (not found), 403 (forbidden), 410 (gone).
5xx: Server error. 500, 502, and 503 indicate a server-side problem.

How redirect chains affect SEO

A multi-step redirect chain slows page loads, dilutes link signals, and can cause crawlers to stop following partway through. Where possible, collapse the chain so the origin links directly to the final destination, and use 301 or 308 for permanent moves.

301 versus 302

A 301 is a permanent move, so search engines transfer indexing and link equity to the new address. A 302 is temporary and tries to keep the original URL in place. For permanent changes like a domain migration or URL restructure, always use 301. To also inspect the cache and security headers of the final response, view the full header set with the HTTP header checker.

Frequently asked questions

What happens when there are no redirects?

Only the single final status code is shown, with no intermediate hops. For example, a direct 200 displays just that one result.

Why might results differ from my browser?

This tool sends a standard request and does not follow JavaScript or meta-refresh redirects. Some servers also return different responses to bots than to browsers.

Can it check internal addresses?

No. For security, requests to private networks, internal IPs, and reserved hosts are blocked. Only public internet URLs can be checked.

Does it download the page body?

No. It only inspects status codes and the redirect path; the response body is not read, which keeps it fast and lightweight.

Is there a limit on the number of hops?

Yes. To prevent loops, the number of redirects followed is capped. If the cap is reached, the last response is shown as the final result.