HTTP Status and Header Checker

How to use it

1. 1Enter the address you want to checkType or paste it into the field marked "Address to check". Include the scheme — https://example.com/ rather than example.com — because http and https can return completely different answers, and which one you meant is not something the tool should guess.
2. 2Press Check and wait a few secondsThe request runs from our server rather than from your browser, so it is not affected by your cache, your extensions or your session. That is the point: it shows what an anonymous visitor gets.
3. 3Read the status code firstIt is the server's one-line answer. 200 means the page was served, 301 and 302 mean it pointed somewhere else, 404 means there is nothing there, and anything starting with 5 means the server itself failed. If this is not what you expected, nothing further down the page will make sense until it is.
4. 4Follow the redirect chainEvery hop between the address you gave and the one that finally answered is listed with its own status. This is where the surprises usually are — a page that loads perfectly in a browser can be arriving via three redirects, and each one costs time and dilutes what search engines pass along.
5. 5Check the headers and the timingsHeaders are the instructions the server sends alongside the page: how long it may be cached, what type of content it is, which security policies apply. The timings split a slow response into DNS lookup, first byte and total, which tells you whether the delay is in finding the server or in the server thinking.
6. 6Share the result while it lastsThe result has its own link you can send to whoever needs to fix it. It is deleted after 24 hours, so copy anything you need to keep — and re-run the check after a change rather than trusting an old link.

About this tool

This tool fetches a URL the way a crawler would and reports exactly what came back: the HTTP status, every response header, the redirect path taken to get there, and how long each stage took.

It is the first thing to reach for when a page "works in the browser" but misbehaves for search engines, uptime monitors or API clients — those see the raw response, not the polished page, and this tool shows you what they see.

Understanding the result

The status code is the server's one-line answer: 200 means success, 3xx means "look elsewhere", 4xx blames the request, 5xx blames the server.

Headers are the response's metadata — caching rules, content type, security policies, cookies. They are shown lower-cased and unmerged, exactly as received.

The redirect chain lists every hop between the URL you gave and the final address, with each hop's status. DNS, first-byte and total timings separate a slow lookup from a slow server.

Example

https://example.com/

HTTP 200 · no redirects
content-type: text/html
cache-control: max-age=…
DNS 12 ms · first byte 89 ms · total 141 ms

Limitations

• The check runs from our server, not your location — a site that geo-blocks or rate-limits our address may answer differently for you.
• Responses larger than our download ceiling are truncated, and the result says so when that happens.
• JavaScript is not executed. A page assembled in the browser still reports its raw HTTP response here — which is precisely what makes the result useful for SEO.
• Requests to private and internal addresses are refused by design.

Questions