HTTP Status Checker
The status code, the final URL after redirects, the response time and every response header of any address, fetched once from our server with no cookies, the way a crawler sees it.
How to use it
- Paste the full address, including the path if you are checking a specific page.
- Press Check status. Our server requests the page once, without cookies, and follows redirects.
- Read the first and final status, the hop count and the time, then open the header list below.
One request, the whole answer
Browsers hide most of what a server says. They show the page, follow redirects silently and never display the headers that decide caching, security policy and how the page may be embedded. This checker makes that single HTTP exchange visible: the status line of the first response, the chain of redirects if any, the final status and URL, how long the server took to answer, and the full header list with session-like values redacted.
It is the quickest way to confirm that a redirect is a 301 and not a 302, that a deleted page really answers 404 or 410, that a CDN is caching (look for Age, CF-Cache-Status or X-Cache) and that the security headers you configured are actually being sent.
HTTP status FAQ
What does the HTTP status code tell me?
The first line of the server's answer. 200 means the page was served, 301 and 302 mean it moved (the Location header says where), 404 means nothing is at that address, 403 means the server refused, 500 to 503 mean the server failed or is overloaded. The checker shows the status of the first response AND the final one after redirects, because the two often differ.
Why does the checker show a different status than my browser?
Your browser sends cookies, a logged-in session and its own user agent; the checker sends a plain request from our server with no cookies. A page that answers 200 for you and 302 to a login page for the checker is behaving correctly for anonymous visitors, which is also what search engines see.
Which headers matter most?
Content-Type (the page type and charset), Cache-Control and Expires (how long browsers and CDNs may keep it), Location (where a redirect goes), Server and X-Powered-By (what runs the site, often best hidden), Strict-Transport-Security, Content-Security-Policy and X-Frame-Options (security), and Set-Cookie. Values that look like session tokens are redacted by the checker before they reach your screen.
Is the response time the same as page speed?
No. The time shown is how long the server took to start answering a single request for the HTML from our location, which is close to the time-to-first-byte metric. A fast first byte can still belong to a slow page if it loads large images and scripts afterwards. Use the Page Speed Checker for the full picture.
Can I check a URL that needs a login?
The checker cannot sign in, so it will show whatever the site serves to an anonymous visitor, usually a redirect to the login page or a 401 or 403. That is still useful: it is exactly what a crawler or a logged-out visitor gets.
More free tools: Redirect Checker · Security Headers Checker · Is It Down? · Broken Link Checker