HTTP Headers and Status Code Checker
See the status code, redirects and response headers: which web server is running, caching rules, HSTS and more.
What the HTTP headers and status code check shows
The tool sends a request to the address and shows how the server responds at the protocol level, without downloading the page itself. You see the status code (for example 200 OK, 301 Moved Permanently or 404 Not Found), the redirect target in the Location header and the server's response headers. It is a first-line diagnostic: it tells you whether the resource is available, where it redirects and what software serves it. The report is invaluable when migrating a site, setting up canonical redirects and figuring out why a URL does not behave as expected.
Headers and what they reveal about the server
Each header carries specific technical information about the platform and its configuration.
| Header | What it tells you |
Server | The web server type and sometimes its version (nginx, Apache, LiteSpeed). |
X-Powered-By | The backend platform or language (PHP, ASP.NET). |
Strict-Transport-Security | HSTS is enabled: the browser always connects over HTTPS. |
Cache-Control | Caching rules for browsers and intermediate proxies. |
Content-Type | The type and character encoding of the content. |
Debugging redirects and hiding software versions
A common problem is a long or looping redirect chain. The Location header at each step shows where the response leads: for example from HTTP to HTTPS, then from www to the bare domain. Extra hops slow down page loads and waste crawl budget, and a loop makes the site unreachable. Also pay attention to versions in Server and X-Powered-By: an exact software version hints at which known vulnerabilities to try, so it is usually hidden or trimmed to the product name. CDN-specific headers such as cf-ray indicate that a content delivery network sits in front of the server.