Home HTTP Headers Checker
HTTP headers checker
readyInspect HTTP response headers for any public URL. Captures content-type, server, security headers (HSTS, CSP, X-Frame-Options, Referrer-Policy), cache directives, and cookies.
How it works
This tool sends the public URL to the Domainee header-check API, which performs a server-side request and returns the response headers as JSON. JustKit does not receive or store the URL. Do not enter private, authenticated, or secret-bearing URLs into a public checker.
FAQ
Why use a remote checker?
Browsers block cross-origin reads of arbitrary response headers. The Domainee API makes the public request and returns a JSON result.
What headers are typically interesting?
Security: strict-transport-security (HSTS), content-security-policy (CSP), x-frame-options, referrer-policy, permissions-policy. Caching: cache-control, etag, last-modified. Server identity: server, x-powered-by. Content: content-type, content-encoding.
Why does the proxy fail on some sites?
The proxy obeys robots.txt and rate limits; some sites block known proxies or require user-agent spoofing. For paid or authenticated endpoints, use curl locally instead.
Does this work for HTTP/2 or HTTP/3?
The proxy negotiates the best HTTP version with the target server; results show the headers returned regardless of protocol version.
Does this save my inputs?
The last URL persists in localStorage. The URL is sent to api.domainee.dev; JustKit does not receive it.