HTTP headers check

Inspect response headers and redirects, with probe locations and TLS verification results.

Remote HEAD request, separate from your browser’s connection.

Redirects are reported at the submitted URL. Enable follow redirects to inspect a bounded chain of up to five responses.

Globalping receives the URL and publishes targets and results. Submit public pages only, without passwords, tokens or personal information.

Example report

Illustrative data. Run a lookup for live results.

HTTP response received

Example report

This is the last status observed along the server-side HEAD request chain. Collection state and HTTP response status are separate; header presence alone does not certify security.

Next step: Inspect redirects, the connected address and raw response headers. Compare the same URL and family after changing the affected server configuration.

HTTP status200
Remote probe
Frankfurt, DEAS64500 · Example probe network
Pinned public address
192.0.2.10
Probe TLS verification
Authorized by probe (TLSv1.3)
Probe updated
  1. Response headers

    Header nameHeader value
    content-typetext/html
    cache-controlpublic, max-age=300
    x-content-type-optionsnosniff
    x-frame-optionsSAMEORIGIN
    serverexample-server
    content-length1256

    Header presence review

    Header nameHTTP status
    strict-transport-securityAbsent in this response
    content-security-policyAbsent in this response
    x-content-type-optionsPresent
    referrer-policyAbsent in this response
    permissions-policyAbsent in this response
    x-frame-optionsPresent
    cache-controlPresent
    content-typePresent
HTTP headers check limits: up to 5 responses, HEAD requests only, 55-second collection deadline. No browser cookies or authorization headers are forwarded.

HTTP headers check limits: up to 5 responses, HEAD requests only, 55-second collection deadline. No browser cookies or authorization headers are forwarded.

Each step is a HEAD request from one named Globalping probe. Redirect steps may use different probes. These are remote observations, not your browser response or a security grade.

On this page

Learn more about HTTP headers check

Run an HTTP headers check for a public website

An HTTP headers check helps answer a practical question: what did a web server return before the page content? Enter a public URL, choose IPv4 or IPv6, and start the check. The result shows response fields, status codes, redirect steps, the selected public address, and the remote probe that made each request.

Read more

This HTTP headers check uses HEAD requests. It collects metadata without asking the probe to download a page body. A normal browser visit usually uses GET, so compare results with that distinction in mind. The method is fixed and visible; the tool does not silently switch to GET when a website rejects HEAD.

Before running an HTTP headers check, remove passwords, access tokens, email addresses and private identifiers from the URL. Globalping receives the submitted target, path and query, and makes measurement results public. The destination receives a request from a remote probe. Google Public DNS receives hostname resolution queries through our server.

The HTTP headers check assumes HTTPS when you omit the scheme. It accepts ordinary HTTP on port 80 and HTTPS on port 443. Other ports, embedded login credentials, local addresses and unsupported protocols are rejected. A URL fragment, such as #pricing, is removed because it is not sent in an HTTP request.

Read the HTTP headers check results

Begin with the HTTP status code and the URL for each step. In an HTTP headers check, a 200 means that this particular request received a successful response. A 404 is also useful evidence: the server answered, but the requested resource was not found. Neither code establishes the quality of the website as a whole.

Read more

A completed HTTP headers check can contain a 403 or 405. The first may reflect an access policy; the second indicates that the method is not allowed for that resource. Those are actual responses, not transport failures. Investigate their values and compare with the website's intended behavior before changing a server configuration.

The header review follows supported redirect responses—301, 302, 303, 307 and 308—when there is one usable Location value and the next destination passes validation. A relative Location is resolved against the current URL. The tool stops on loops, ambiguous locations, unsupported destinations, incomplete responses or the five-response limit.

Each step in the header review includes its probe city, country, network, ASN and update time. Steps may use different Globalping probes. Treat the chain as a sequence of individually observed responses, not a single persistent browser session. Geographic routing, server changes or access controls can affect which result each probe sees.

Interpret header presence without a score

The header review in this header review uses three states. Present means a named field was returned. Absent applies to a complete response in which that field was not found. Not tested or incomplete means there is insufficient evidence to call it absent. The review does not validate every directive or simulate browser enforcement.

A security headers checker should explain its evidence rather than award a reassuring grade from a field count. This header review deliberately shows the actual values beside a limited presence review. A field can exist with an ineffective, malformed or unsuitable value. A missing field may also be irrelevant to a non-document response.

Keep TLS evidence separate

This header review displays the TLS authorization result reported by the probe. Globalping can collect headers even when its certificate verification does not succeed. Such headers are shown as observations from an unverified connection, and this tool stops before following another redirect. It does not label that result a trusted HTTPS response.

Limits, privacy and troubleshooting

A header review has a collection deadline of 55 seconds and a maximum of five measured responses. Each submitted probe has a ten-second measurement timeout. Network delays, service availability and rate limits can prevent a complete chain. When the limit is reached, the last redirect may be visible even though its destination was not requested.

Read more

The header review preserves collected steps when a later lookup or provider request fails. Inspect the stopping reason before interpreting the chain. An empty or partial result is not evidence that all security headers are missing. Retry after checking the hostname, address family and public availability, rather than repeatedly submitting the same failing request.

Some servers return long fields or many cookies. The header review marks a shortened provider response and stops further redirects, because truncated evidence may omit or alter an important field. Review the public source measurement where appropriate, but do not assume it contains data the probe itself never retained. Header values are displayed as text.

Stop collection ends this page's wait, but a header review already submitted to Globalping may still finish there. Clearing the form removes local inputs and displayed results; it does not retract a public measurement. Do not use this tool for private URLs. Copied reports contain the submitted URLs and response values, so review them before sharing.

HTTP headers check questions

Does the HTTP headers check download my page?

It requests headers with HEAD and does not intentionally request a response body. A server can implement HEAD differently from GET or reject it altogether. The HTTP semantics standard defines that method; the result here records the response actually observed, including a method rejection.

HTTP semantics standard

Why does an HTTP headers check differ between runs?

The selected public address, probe location and time can change. Load balancing, staged deployments and regional policies can produce legitimate differences. Compare the recorded source details before treating a changed field as a regression. For a repeatable deployment test, also use a controlled client with an explicitly chosen destination and request configuration.

Can an HTTP headers check verify my VPN?

No. This request originates from a remote Globalping probe, not through your browser's VPN tunnel. Use IP comparison to compare browser-visible exits, and understand each separate test's limitations. Response fields describe a website's reply to the probe; they do not establish whether your own traffic is protected.

IP comparison

What should I save from an HTTP headers check?

Keep the URL, method, address family, selected address, probe identity, timestamps and relevant field values together. The copy action includes this context and links to the public source measurements. Describe incomplete steps explicitly when reporting a problem. A screenshot of one header without its request context can lead to the wrong diagnosis.

Implementation and source behavior were checked on September 28, 2026. Probe transport details are documented in the Globalping HTTP implementation; provider limits and measurement access are described in the Globalping API reference. The HTTP headers check uses those observations within the narrower limits stated above.

Globalping HTTP implementation

Globalping API reference

Why can a website work in my browser but reject this request?

The probe uses HEAD, whereas an ordinary page visit usually uses GET. A server can handle those methods differently. A returned 405 is response evidence; the tool does not silently switch methods to manufacture a successful page result.

Why does the last redirect have no following response?

The tool validates each next destination and limits the chain. A loop, ambiguous Location, unsupported target, incomplete response or response limit can stop collection. Read the stopping reason before assuming the destination itself failed.

Does the presence review validate a Content-Security-Policy?

No. A present field is not necessarily effective or suitable for the application. The review preserves values and incomplete states without simulating every browser policy. A security assessment requires context beyond counting returned header names.

Can I include an access token in the query string?

Do not submit private identifiers or secrets. Globalping receives the URL path and query, and measurement results are public. Remove sensitive values before starting; clearing the local result does not remove an already submitted remote measurement.