Investigate HTTP headers and redirect chains

How to use the workspace

1. Enter a public HTTP or HTTPS URL without credentials or confidential query parameters.
2. Keep HEAD unless you specifically need GET behavior. GET is explicit and can have side effects on a poorly designed target.
3. Submit, then inspect the hop table and individual response headers. Check the termination reason before treating the chain as complete.

A concrete starting point

URL: https://example.com
Method: HEAD
Read: status code, Location, Cache-Control, Content-Type

The target is contacted by the diagnostics service only after submission, never opened automatically in your browser.

Read the result carefully

Each hop preserves its URL, method, remote address, elapsed time and duplicate header pairs. A 301 or 302 describes a redirect; the following hop is a separate observation. A timeout, blocked destination or loop may yield a partial report.

Common mistakes to avoid

• HEAD and GET can produce different headers. This tool does not silently switch methods.
• A response header is not a complete security assessment.
• Private destinations and unsafe redirect targets are blocked; this is not a tool for reaching your internal network.

Limits & privacy

Up to five redirects and six hops, bounded headers and a 12-second API deadline. Remote response bodies are not displayed. No cookies or custom credentials are forwarded.