About this http headers lookup
HTTP headers are the short messages a web server sends before the page itself. They tell the browser how long to cache a file, which type of content comes next, whether to upgrade to HTTPS, which security rules apply and which software answered. Reading them is the first step when a page is slow, cached wrongly, blocked by a policy or served from a different place than you expected.
This tool makes a request from our server, follows up to five redirects by hand, and lists the headers of the final response together with the status code, the protocol used, the connection time and the address of the server. If a CDN or hosting platform leaves a recognisable header, such as cf-ray for Cloudflare, it is named as a hint. Look for strict-transport-security, content-security-policy, x-content-type-options and cache-control when auditing a site.
Every redirect is checked before it is followed, and addresses on private or reserved networks are refused, so the tool cannot be pointed at internal systems. The address you type is sent to our API at /api/http-headers-lookup.php. We do not store searches, though the web host's access log can contain the request. Only the headers are kept in memory for the answer; the page body is not read.
Which controls should I check first?
The HTTP Headers Lookup form labels its controls as Website address. Use those labels to keep the source and settings separate. A sample argument that selects a mode is not additional source text. Choose the setting matching your intended operation before copying a result, and change it explicitly when comparing another mode. The labels describe what this form accepts; the worked examples below demonstrate only the stated supplied values.
How should I interpret this specific operation?
Headers describe a particular HTTP response. A redirect response and its final destination may have different headers, and an application can vary them by route or request conditions. Separate a status code from a header value when documenting an observation. A server header is a claim in the response, not a complete software inventory. Security-relevant behavior requires checking the applicable request and browser context rather than treating one header dump as a full site audit.
Worked helper values
These values come from the reproducible calculation examples supplied with this tool. Each row identifies the complete supplied arguments and the returned value. A visible ↵ denotes a line break and ⇥ denotes a tab in text examples. Settings appear alongside source data so that a different mode is not mistaken for an identical input. These are helper calculations, not observations of a live device, fetched target, image decoder, browser preview or downloaded file. Use the stated method above to relate the returned fields to the actual operation.
| Supplied values | Calculated return value |
|---|---|
| http-headers-lookup; a b.com | /api/http-headers-lookup.php?q=a%20b.com |
| example.com ; x | example.com |
Whose network view does this result represent?
A server-side check observes the target from the checking service's network location. Your browser, a mobile connection and another resolver can see different answers because of caching, geolocation, routing, filtering or load balancing. Keep the exact queried target and the time of your check when comparing observations. A timeout means this attempt did not obtain a result within its limit; it does not prove the target is unavailable everywhere. To investigate a discrepancy, compare the same target and protocol from the relevant client environment as a separate step.
How should I prepare a target?
Use a public target whose spelling and scope you can explain. A hostname, an IP address and a complete URL carry different information. A URL includes a scheme, path and possibly a query string, while a hostname identifies a host without those request details. Follow this page's stated input convention and omit credentials or confidential query values from demonstration targets. Correct an invalid-target message before retrying. The address is sent to the checking service for processing, so this workflow is different from a local parser that merely splits the supplied text into components.
What can I infer from missing fields?
A missing field can reflect the target, the available response or the check's scope. It should not be replaced with a guessed value. Read any status or explanation beside the output and distinguish an empty answer from an error. Compare the same type of evidence across repeated checks rather than treating every field as an independent verdict. A registration record, resolver result and HTTP response describe different layers and can disagree without any of them being fabricated. Follow a discrepancy to the layer it concerns before changing DNS, application settings or certificate configuration.
How can I document a reproducible observation?
Record the exact input, result fields that matter, and any timeout or error text. If the target is a URL, preserve the path and protocol because checking the homepage can differ from checking a specific resource. When a value appears to change, repeat a narrowly scoped check and compare the complete response, including intermediate context if the tool exposes it. Avoid attributing a difference to a named provider or person based only on one field. These outputs are observations from a limited check, not a record of ownership or an exhaustive audit of every configuration on the target.
Which security headers should a website have?
At least strict-transport-security, x-content-type-options and a content-security-policy or frame-ancestors rule. The right set depends on the site.
Why do headers differ from what my browser shows?
Servers can answer differently by location, language, cookies and user agent. This tool sends a plain request from our data center.
What happens when the page redirects?
Redirects are followed up to five times. Each step is shown in the chain, and the table lists the headers of the last response.
Can I check a page behind a login?
No. The request carries no cookies or credentials, so you see the public response only.