Short answer: A redirect check follows a short public HTTP or HTTPS chain and records status, location and timing for each hop. It identifies loops and unexpected schemes without forwarding cookies or credentials. The result is a bounded server observation, not a browser navigation or security audit. This page gives a bounded public observation for Redirect Checker, not a universal promise about every user, provider or future request.
What it measures
The tool validates URLs, resolves public hosts and stops after four hops. It records status and Location while omitting cookies and authorization headers to limit SSRF exposure. Read the form status and result together. A missing or unavailable upstream response is different from a clean result, and the submitted input must remain attached to the evidence.
Protocol and standards
RFC 9110 defines HTTP redirect semantics. MDN documents 301, 302, 303, 307 and 308, while the WHATWG URL Standard explains parsing and serialization. The linked primary references explain the terminology and normative boundaries. Implementations, caches, trust stores, resolver behavior and operator policy can still affect a live observation, so standards should guide interpretation rather than replace it.
Inputs and validation
Enter an absolute public http or https URL. Unsupported schemes, credentials, private targets and malformed locations are rejected. Do not paste signed or session URLs. Use only the public value requested by the form. Remove credentials, fragments, private addresses and unrelated paths. Validation protects the upstream request and prevents private material from entering a diagnostic workflow.
Outputs and evidence
Each hop reports status, public Location and bounded timing. A final 200 is only a successful bounded response; a loop or hop limit is routing complexity. Preserve the input, status and check time when sharing the result. Empty, unavailable and positive responses have different meanings. Do not combine rows from separate checks without keeping their names, protocols and timestamps visible.
Worked example
A 301 from https://example.com to https://www.example.com followed by 200 is a two-response path. It does not prove browser cache or POST behavior. This is an explanatory example, not a claim that the same value exists for another domain or endpoint. Re-run after a controlled change with equivalent inputs so the difference can be attributed safely.
How to interpret the result safely
Prefer one intentional canonical hop and verify scheme, host, path and query. Permanent statuses can be cached; a loop means layers disagree about the canonical URL. First ask whether the tool measured the question you actually have. Then compare an important conclusion with an independent source such as provider configuration, a real message, an authoritative registry, a browser observation or an operator log.
Limitations and upstream behavior
Method, headers, cookies, cache, geography and JavaScript can change navigation. No browser or authenticated flow is simulated; four hops is the maximum. Network location, cache state, rotation, rate limits and policy can change public results. Use the upstream operator documentation for remediation or account action. This tool reports uncertainty instead of inventing a value.
Troubleshooting checklist
- Enter a complete public http or https URL.
- Inspect the exact Location and next public host.
- Compare browser method, cache, cookies and user agent when results differ.
Key takeaways
- The tool validates URLs, resolves public hosts and stops after four hops. It records status and Location while omitting cookies and authorization headers to limit SSRF exposure.
- Prefer one intentional canonical hop and verify scheme, host, path and query. Permanent statuses can be cached; a loop means layers disagree about the canonical URL.
- Method, headers, cookies, cache, geography and JavaScript can change navigation. No browser or authenticated flow is simulated; four hops is the maximum.
FAQ
Are credentials forwarded?
No. Requests omit cookies and authorization headers.
What is a redirect loop?
A chain returns to an earlier target or never reaches a final response.
Is 301 always best?
No. Permanence, method and caching intent determine the status.
Does 200 prove usability?
No. It proves only a successful final bounded response.
Sources
Primary references used for this guide: