HTTP Inspector screenshot

HTTP Inspector

Inspect a public URL's HTTP version, compression, HSTS, CSP, security headers and range support from the server side.

Privacy First
0 Runs
Updated 2026-11-07
Runs on the tool server
No account needed
Public URLs only
No redirects followed

What this HTTP inspector does

Ask the server what it actually sends: the status line and protocol, the security headers, HSTS and CSP values, whether the body is compressed, whether byte ranges work, and whether TLS negotiates HTTP/2. A browser cannot answer these, because CORS and the page's own protocol hide them, so this is one of the few tools here that asks the server.

How to use it

Enter a public https:// URL, choose a check and run it. The answer is a JSON report of observed values rather than a score: a missing header is null and also listed under missing_security_headers, and a redirect is reported instead of followed.

Privacy and safety

The server fetches the URL you name, so this page says so instead of repeating the tool page's "nothing is uploaded" promise. Private, loopback and reserved addresses are refused before a connection is opened, redirects are not followed, and at most 256 KB of the body is read.

Enter a public URL and choose a check, and this page asks the server itself — from the tool server, not your browser — what it actually sends back: its HTTP version, compression, HSTS header, content security policy, or range support.

It is the server-side answer because a browser cannot see a response's ALPN negotiation, its transfer encoding or its HSTS header for a cross-origin URL without CORS allowing it. Here the request is made by the tool server with its own user agent.

The request follows no redirects, reads at most 256 KB of the body and refuses any host that resolves to a private, loopback, link-local or reserved address.

The six checks

Overview reports the status code, the HTTP version, any redirect target without following it, the content type, the server header, the six security headers and which of them are missing.

Compression sends an accept-encoding header for gzip, deflate and brotli and reports the content encoding alongside the decoded and transferred byte counts. HSTS parses the header for max-age, includeSubDomains and preload, and flags a max-age below 180 days.

CSP reports the enforced policy, or the report-only one when that is all there is, with its first 25 directives. Range sends `bytes=0-99` and reports whether the answer was a 206. The HTTP/2 check is a raw TLS handshake asking for `h2`, so it only works on an https URL.

  • overview, http2, compression, hsts, csp, range
  • No redirect following, 256 KB body cap
  • User agent: AllToolsHttpInspector/1.0

Reading the result without over-reading it

A missing security header is a fact about this one response, not a verdict on the site: a CDN may add the header at the edge, and a redirect may be answered by a different host than the final page.

Because redirects are not followed, inspecting a URL that answers 301 tells you about the redirect, not about the page it points to. Submit the final URL as well.

How to use the URL and check

Enter the public URL, choose the check, HTTP version, compression, HSTS header, content security policy or range support, and run. The server-side request follows no redirects, reads at most 256 KB, and refuses private, loopback, link-local and reserved hosts.

Read what the server itself sent back under its own user agent: the ALPN version, the transfer encoding, the headers. A browser could not see these cross-origin without CORS; the tool server can.

What to Expect

Best for

  • Checking whether a server sends HSTS with a long enough max-age
  • Seeing which security headers are missing from a response
  • Confirming whether a host negotiates HTTP/2 over TLS

Not ideal for

  • A private, internal or loopback host, which the guard refuses
  • A page behind a login, which this request does not have
  • Following a redirect chain, which is deliberately not done

What this tool keeps

  • The status code, HTTP version and headers as sent
  • The redirect target, reported rather than followed
  • The decoded and transferred byte counts side by side

What may need cleanup

  • A header added by a CDN rather than by the origin
  • The verdict on a URL that redirects, which describes the redirect
  • A CSP with more than 25 directives, of which only the first are listed

Common errors

  • Inspecting a private address and reading the refusal as an outage
  • Expecting the HTTP/2 check to work over plain http
  • Reading a missing HSTS header on a redirect as a missing header on the site

Example use cases

  • An HSTS rollout check before and after a change
  • A security-header review of a public endpoint
  • Confirming that compression is enabled for a static asset

Sample input

The overview check against a public https URL.

Sample output

A status code, an HTTP version, the security headers present and the list of those missing.

Who this is for

  • Developers checking response headers
  • Security reviewers auditing a public endpoint
  • Anyone troubleshooting compression or HTTP/2

Frequently asked questions

What does the HTTP inspector ask a server?

Its HTTP version, compression, HSTS header, content security policy or range support, requested from the tool server rather than your browser.

Does it follow redirect chains?

No. A redirect target is reported rather than followed, so the verdict describes the redirect.

Can I inspect an internal or loopback host?

No. The guard refuses private, internal and loopback hosts.

Developer program

Build custom tools for your store

Join the SDK program to create useful ecommerce utilities for your store.