Proxy tools

HTTP headers checker

Request a public URL and see its response headers, the redirect chain and whether common security headers are present.

A HEAD request is sent from our server to the public URL you enter. Only ports 80, 443, 8080 and 8443 are allowed.

How it works

What this tool does

  1. We send a HEAD request

    Our server requests only the headers of the URL you enter.

  2. We follow redirects safely

    Each redirect target is re-validated as public before we follow it, up to 5 hops.

  3. We check security headers

    The tool marks the presence of key headers on the final response.

How to read the result

  1. Missing headers are signals, not automatic faults; their importance depends on the site. HSTS and X-Content-Type-Options are widely recommended.

  2. Only ports 80, 443, 8080 and 8443 are allowed, and private or internal addresses are blocked.

In depth

The details that decide the outcome

HEAD requests, pinned connections and safe redirect following

The tool sends a HEAD request, which asks for the status line and headers a GET would return but no body. It sets Accept-Encoding to identity, identifies itself as BuyProxy-HeadersChecker/1.0 and gives up after eight seconds. Because it is a script, not a browser, a site may answer differently: some servers return 405 or 501 for HEAD, and bot rules or CDN challenges can show 403 where a browser sees the page. Header names are shown in lower case, and repeated headers are joined with commas. The response is the one this tool received, not necessarily what your browser would get.

Redirects are where a fetcher can be abused, so each hop is checked again. The Location value is resolved against the current URL, the scheme must be http or https, credentials inside the URL are refused, and the port must be 80, 443, 8080 or 8443. The host name is resolved and every address must be public; the socket then connects to that exact verified address while the Host header and TLS server name stay the host name. That pinning defeats DNS rebinding. Up to five redirects are followed, so a typical chain of http, https and www uses three or four requests.

Worked reading: a redirect chain and a security-header checklist

Illustrative chain: http://example.org returns 301 to https://example.org, which returns 301 to https://www.example.org, which returns 200. That is two redirects, so three requests before any content, and a visitor on a slow link pays for each one. The fix is a single hop from the plain-HTTP address straight to the final HTTPS host. Note that this tool does not enforce HSTS, so an http:// URL is requested as written, which is useful because it shows what a first-time visitor receives. If the list still shows a redirect after five hops, you are looking at a loop or an unusually long chain.

Then read the checklist. A missing header is a signal, not an automatic fault, and its weight depends on the site; the table summarizes what each of the six checked headers does. Remember too that this request comes from this site’s server and not through your proxy, so country-specific redirects or content reflect the server’s location. To see what your proxy exit receives, run the same request through your own client. Redirect behavior and headers can also differ between HEAD and GET, so confirm important findings with a normal browser request.

HeaderWhat it doesWhen a missing header matters
strict-transport-securityTells browsers to use HTTPS only for the hostHTTPS sites that should never load over HTTP
content-security-policyRestricts where scripts, frames and other resources may load fromSites with user content or third-party scripts; needs per-site design
x-content-type-optionsThe nosniff value stops browsers guessing content typesAlmost any site; low cost and widely recommended
x-frame-optionsControls whether the page may be framedPages open to clickjacking; CSP frame-ancestors is the modern form
referrer-policyLimits referrer information sent to other sitesPages whose URLs carry sensitive details
permissions-policyRestricts browser features such as camera or geolocationPages embedding third-party content

FAQ

Tool questions

Why HEAD and not GET?

HEAD returns headers without the body, which is lighter and safer.

Some servers reject HEAD — what then?

They may return an error status; that response is shown as-is.

Can it check pages behind login?

No, only public URLs.

Why does the headers checker show 403 or 405 when my browser loads the page?

The tool uses HEAD from a server address with its own user agent. Some sites reject HEAD, challenge unfamiliar clients, or apply geographic and bot rules that a browser session passes. The status shown is the real answer to this request, so confirm in your browser’s developer tools.

What happens if a site redirects more than five times?

The tool follows at most five redirects and then stops, showing the chain gathered so far with the last status, which will still be a 3xx. That usually means a redirect loop, for example between two hosts or between HTTP and HTTPS, and the fix is on the site being tested.

Not sure which plan fits?

Describe your use case and target countries and we will recommend a product — or tell you honestly when another type suits you better.