HTTP Status Checker
See the status code any URL returns.
Checked from our server. One location, so results show reachability from there only.
What the HTTP status checker does
Every time a browser asks for a page, the server replies with a three-digit status code before anything else. The HTTP status checker sends that request from our server and shows you the code, what it means in plain words, the response headers and how long the answer took.
It’s useful when you’ve moved or deleted pages and want to confirm the old addresses now return 301 or 410, when a monitoring alert mentions a 5xx error, or when you need to see which headers a server sends, such as Cache-Control or HSTS, without opening your browser’s developer tools.
How to use the HTTP status checker
- Paste a URL. If you leave off https://, we add it.
- Tick Follow redirects to see where the URL finally lands, or leave it off to see the first response only.
- Press Check status. You get the code, what it means, the safe response headers and how long it took.
Understanding the results
Status codes come in families. 2xx means success, and 200 is the normal answer for a working page. 3xx is a redirect, and the Location header says where to go next. 4xx means the server won’t or can’t serve this request, such as 404 for a missing page. 5xx means the server itself failed; 502, 503 and 504 often point to an overloaded server or a problem behind a proxy. If no code appears at all, the connection failed before any answer arrived, and we show the reason, such as a timeout or a refused connection.
The time line splits the total into DNS lookup, connection and first byte. A slow first byte usually means the server is slow to build the page. Protocol shows whether the server spoke HTTP/1.1 or HTTP/2, and Server IP is the address we connected to. When the URL redirects and you didn’t follow it, the result shows the next address and offers a link to trace the full chain.
Questions
Why do I get 403 here when the page opens in my browser?
Many sites use bot protection that blocks automated requests like ours. A 403 or 429 usually means the server is up but refused us.
Which headers are shown?
Common, safe headers such as Server, Content-Type, Cache-Control and security headers. Cookie values are always hidden.
How is this different from the redirect checker?
This tool focuses on one response and its headers. With Follow redirects ticked it lists each hop’s status, but the redirect checker adds the time, protocol and address for every hop, with notes on what to fix.
Can I check a URL on another port?
No. Only the standard web ports can be checked: 80 for http:// and 443 for https://. Addresses that contain a username or password are refused too.
Where is the request made from?
Checks run from our server, in one location, so results show what that location sees.