HTTP Header Checker
Check the status and HTTP response headers of a public web URL.
Check Results
- Final URL
- Redirect count
| Header name | Header value |
|---|
These headers reflect the server response at check time. Results can vary by browser, region, and CDN state.
What Can HTTP Response Headers Show?
HTTP response headers describe content type, caching, compression, redirect targets, and security policies. They help verify that CDN, cache, and security settings are delivered as intended after deployment.
Headers worth checking after deployment
Content-Type confirms how a response is interpreted, Cache-Control governs reuse, Content-Encoding reveals compression, and Location identifies a redirect target. CSP and HSTS are security controls, but their presence alone does not prove that a site is securely configured.
What this server-side view represents
Utilook requests the public URL from its own server and reports that response. A CDN, geographic rule, authentication layer, or user-agent rule can make your browser receive different headers, so compare with browser developer tools when location-specific behavior matters.
Frequently Asked Questions
Which HTTP headers can I inspect?
You can inspect general, caching, and security response headers returned by the server, such as Content-Type, Cache-Control, Content-Encoding, Location, and Content-Security-Policy.
Does the checker use HEAD or GET?
It uses HEAD first to avoid receiving a response body. If the server rejects HEAD with 405 or 501, it retries with GET to inspect the headers and does not store the body.
Does it follow redirects?
Yes. It follows up to five Location redirects, validates every destination again, and displays the final URL's response headers.
Can I check internal addresses or custom ports?
No. To prevent server abuse, only public addresses and the standard HTTP 80 or HTTPS 443 ports are allowed. Local, private, reserved, and special-use targets are blocked.