HTTP Header Inspector
Fetch any URL and see the raw HTTP response headers the server actually sends, status code, caching directives, content type, cookies, and redirect targets. The web debugger's stethoscope.
How to use
- Enter the full URL (https://example.com/page).
- Click Run to fetch it server-side.
- Read the status code and headers, redirects show their Location target.
Every HTTP response carries metadata that browsers act on silently: how long to cache, what content type to expect, where a redirect leads, what cookies to set. When something behaves oddly, a stale page after a deploy, a redirect loop, a download instead of a rendered page, the headers are where the explanation lives.
The usual suspects: Cache-Control decides whether a CDN or browser may reuse a response and for how long. A max-age that is too long explains 'my deploy is invisible', while no-store on a heavy page explains a slow site. Content-Type mismatches make browsers download HTML or refuse to run JavaScript modules. Location on a 301/302 shows exactly where a redirect chain goes, chase it hop by hop to find loops or the http-to-https-to-www chains that waste latency. Set-Cookie exposes whether session cookies carry Secure, HttpOnly, and SameSite attributes. Server and X-Powered-By reveal (sometimes too much) about the stack.
Checking from a neutral server matters: your browser sends cookies, its cache interferes, and extensions mutate requests. This tool fetches cold from Velona's server, the same view a crawler or a fresh visitor gets.
One subtlety: many servers answer HEAD and GET differently, and some CDNs vary responses by User-Agent or geography. If results differ from your browser's DevTools, those are the first variables to suspect.
Examples
Input: https://example.com
Output: HTTP/2 200 · content-type: text/html; charset=UTF-8 · cache-control: max-age=86400Input: http://example.com
Output: HTTP/1.1 301 Moved Permanently · location: https://example.com/Frequently asked questions
Why do I see different headers than my browser's DevTools?
Your browser sends cookies, conditional-request headers, and a different User-Agent, and may be served from cache or a different CDN edge. This tool fetches cold from a server, which is also what search crawlers see.
How do I debug a redirect loop?
Fetch the URL, note the Location header, fetch that, repeat. Loops are usually a CDN forcing https while the origin redirects back to http, or a www/apex rule fighting a trailing-slash rule.
What Cache-Control value should my pages send?
Static assets with hashed filenames: public, max-age=31536000, immutable. HTML that changes: something short like max-age=300, or no-cache with ETags so clients revalidate. The wrong one causes stale deploys or needless load.
Which cookie attributes should I verify in Set-Cookie?
Secure (HTTPS-only), HttpOnly (invisible to JavaScript, blunts XSS session theft), and SameSite=Lax or Strict (CSRF mitigation). Session cookies missing these are a finding in any security review.
Related tools
Velona is India's INR-native AI API gateway with 300+ models, UPI top-up from ₹10, no foreign card needed. These tools are free forever.