See the status code and full response headers returned by any URL.
Every time a server answers a request it sends back a status code and a set of HTTP response headers: metadata describing the response. Headers declare the content type, how long the page can be cached, which compression was used, what cookies to set, and which security policies the browser should enforce. They are invisible in normal browsing but decide a great deal about how a page loads, caches, and is protected. This tool fetches any URL and lays out the status line and every response header it returns.
Enter a URL and the checker reports the final status code, the URL it resolved to after any redirects, and a sorted table of every header with its value. It is handy for confirming a page returns 200 rather than a soft 404, checking Cache-Control and Content-Type are set correctly, verifying security headers like Strict-Transport-Security and Content-Security-Policy are present, and inspecting which server or CDN is in front of a site. Developers and SEOs use it to debug caching, redirects, and indexing issues without opening browser dev tools.
Browsers restrict reading the raw headers of another origin, so the request is made from Reslug servers rather than your browser. The URL is used only to fetch the response and is not stored.
Paste the address you want to inspect into the URL to inspect field, including https:// if you have it.
Click Check headers. The tool requests the URL, following redirects to the final response.
The Response card shows the final status code and the URL it resolved to, so you know whether the page loaded, redirected, or errored.
The Headers table lists every response header alphabetically with its value, ready to copy or compare.
Cache-Control tells browsers and CDNs how a response may be cached and for how long, using directives like max-age, no-cache, and immutable. Getting it right makes repeat visits faster; getting it wrong means either stale content or unnecessary re-downloads. The checker shows the exact value a URL returns.
Common ones are Strict-Transport-Security (forces HTTPS), Content-Security-Policy (limits where resources can load from), X-Content-Type-Options, X-Frame-Options, and Referrer-Policy. Seeing which are present and which are missing is a quick way to gauge how hardened a site is.
The tool follows redirects, so the status and headers shown are for the final response. If you entered an http link that forwards to https, or a URL that 301s elsewhere, the Final URL field shows where the request actually ended up.
No. This tool reports the response headers the server sends back. The request headers are set by the tool when it fetches the page and are not part of what you are inspecting.
No. The request runs on Reslug servers because browsers cannot read another origin’s headers, and the URL is used only to fetch the response, not saved.
Reslug shows you status, clicks, and destination health for every short link you create — not just one-off checks.