Redirect Checker

A 301 says the move is permanent: browsers cache it aggressively and search engines transfer the old URL's signals to the new one. A 302 says the move is temporary: the original URL stays indexed. The subtle part is method handling: both 301 and 302 permit clients to turn a POST into a GET on the next request, which is why 308 and 307 exist as the strict method-preserving versions. This 301 redirect checker shows the exact code at every hop plus its method semantics.

A redirect chain is more than one redirect between the link and the final page, for example HTTP to HTTPS to a trailing-slash URL. Each hop costs every visitor a network round trip, and search crawlers follow only a limited number of hops before giving up. Chains are rarely fatal but always waste: when you control the link, point it directly at the final URL. The trace above counts HTTP redirects and document transitions separately, so the number is real.

Paste the URL above. If the chain revisits a URL it already passed through, the trace stops and reports a loop explicitly. Browsers show users an error page in that situation, so a loop means the URL is effectively down. Loops usually come from conflicting rules: a plugin redirecting to HTTPS while the server redirects back, or two pages redirecting to each other.

The trace sends a normal GET with a desktop browser user-agent, disclosed below the result. Some large sites answer automated clients differently: they may rate limit, block, or serve alternate responses. The path of redirects up to that point is still exact; only the final page's answer can differ. Meta refresh redirects are followed from the HTML; JavaScript redirects are flagged but not followed because that needs a real browser.

HSTS is a browser mechanism: after a site sends the Strict-Transport-Security header once, the browser upgrades future http:// requests to HTTPS internally, before any network request. A server-side tracer observes the server's own 301/308 upgrade instead. When a hop carries an HSTS header, it appears in that hop's response headers in the trace, so you can see the policy that browsers will cache.

The URL is sent to the DevDome server, which requests it and each subsequent hop; the destination sites see those requests. Results are returned to your browser and not stored, shared or sent to analytics. Avoid tracing URLs whose query strings carry secrets like password-reset tokens; the strip-query option removes the query string before tracing, and the tool warns you when a URL looks sensitive.