HTTP Status Check
Send a GET request to any URL or IP and inspect the HTTP status code, reason phrase and key response headers — only headers are fetched, never the full page.
Frequently asked questions
It sends a real GET request from our server to the URL you enter and reports the HTTP status code, reason phrase and key response headers. Only the response headers are read — the page body is never downloaded.
1xx is informational, 2xx means success, 3xx means redirection, 4xx is a client-side error (bad URL, missing permission, not found) and 5xx is a server-side error. The most common codes are explained individually; others fall back to the class explanation.
If you type a host without a scheme (e.g. rss.bz), we assume https://. When the HTTPS connection fails before any HTTP response — for example the site only serves plain HTTP — the check is retried once over http://. If you type the scheme yourself, it is used exactly as given. IP addresses can be entered directly.
It reports the first response only, including the Location header, so you can see exactly where a redirect points. Following redirects automatically would hide the original status code and could be abused to reach internal services.
Key headers such as Server, Content-Type, Content-Length and Location are highlighted, and the full list can be expanded. Cookie headers are never returned, and very long values are truncated.
The request comes from our server, so geo-blocking, CDN steering, firewalls and cache state can make the same URL return a different status than on your machine. That difference is often exactly what you want to diagnose.
No. Query contents are never stored.