HTTP Inspector
Inspect redirects, HTTP status codes, response headers and basic transport behavior for one public URL.
Inspect an HTTP endpoint
What HTTP Inspector checks
This is a single-endpoint diagnostic rather than a worldwide comparison. It makes a bounded request, follows redirects, records each status and Location value, and reports the final headers without downloading a large response body.
What response headers tell you
Cache-Control, Expires, ETag and Last-Modified describe caching and revalidation. Security headers such as HSTS, CSP, X-Content-Type-Options and Referrer-Policy communicate browser policy. Server and Via can reveal parts of the delivery path.
Redirect status codes
301 and 308 communicate a permanent move; 302 and 307 are temporary. The 307 and 308 variants explicitly preserve the request method. Redirect chains should normally be short to reduce latency and configuration risk.
Frequently asked questions
What does HTTP Inspector check?
It follows a bounded redirect chain, records every status and Location header, and shows the final response headers and timing.
What is the difference between 301, 302, 307 and 308?
301 and 308 are permanent redirects; 302 and 307 are temporary. The 307 and 308 codes explicitly preserve the HTTP method.
What is HSTS?
HTTP Strict Transport Security tells compatible browsers to use HTTPS for the host for a declared period.
Why should redirect chains be short?
Every extra hop adds DNS, connection and response latency, and increases the chance of configuration mistakes or loops.