Skip to content
🌐

HTTP Status Checker

Developer

Send a browser request and report the actual HTTP status and exposed headers.

0
0
HTTP status

Only response data exposed by the browser is available. Cross-origin servers must allow CORS.

HTTP status code checker that sends a request from your browser and shows the status line, such as HTTP 200 OK, with the final URL and the headers the browser exposes. Enter an absolute http or https URL to check its live response.

See more about the HTTP Status Checker

The response must be readable by the browser, so a cross-origin server needs to allow CORS, and redirect hops are not listed.

Examples

URL with credentials

https://user:pass@example.com → Enter an absolute HTTP(S) URL without embedded credentials.

URLs with a username or password are refused. Only http and https addresses are accepted.

Blocked by CORS

Cross-origin URL without CORS headers → Request failed: … The server may not allow browser CORS requests.

A status is shown only for responses the browser may read. Requests time out after 10 seconds.

Key features

  • Status line from the browser
  • Final URL and redirect yes or no
  • Readable response headers
  • Last 10 checks kept in the session

Related Blog Posts

Quick answers for HTTP Status Checker

Why can I not see the status for some sites?
The browser only reads responses that the server allows. A cross-origin server without CORS headers blocks the request, and the tool shows Request failed with a CORS hint.
Does it follow redirects?
Yes, the browser follows them. The tool shows the final URL and whether a redirect happened, but not each hop.
Can I send a request body or custom headers?
No. The methods are GET, HEAD, OPTIONS and POST, with no request body or custom headers, and the response body is not shown.
Does the check run from Toolblip servers?
No. The request goes straight from your browser to the target, so the result reflects your network and location.