Plain Tools

Site Status Checker

This tool gives you a fast browser-side way to test whether a URL responds to a simple HEAD request and how long that response takes. It is useful when a website feels slow, appears unavailable, or needs a quick reachability check before you spend time troubleshooting DNS, application code, or local network settings. Because the request is made directly by your browser, the result reflects what your own connection can reach rather than what a remote Plain Tools server can reach.

That direct approach also means the page is honest about limitations. Some sites block cross-origin browser probes or reject HEAD requests even though the service itself is up. When that happens, this checker reports the browser failure instead of pretending the site is down. In practice, that makes it a good first-pass diagnostic tool: if the page responds cleanly, you have a quick baseline. If the probe is blocked, move to a dedicated status page or a same-origin test endpoint to separate application outages from browser policy restrictions.

Open the tool

This page embeds the live network workflow directly, so there is no extra click between the explanation and the check.

Back to Network Tools

Site Status Checker

Run a direct browser HEAD request, then review HTTP status and response timing. The check runs directly from your browser and does not use a Plain Tools proxy.

HEADResponse timingPrivacy-first

How it works

This checker performs a direct browser HEAD request to the URL you enter. It is private by design because there is no Plain Tools proxy, but that also means sites can block the check through CORS or HEAD restrictions.

Frequently Asked Questions

Quick endpoints

This tool only performs a browser-side HEAD request. If a site blocks CORS or HEAD, the browser will stop the check before any reliable status result is exposed.

How this check works

  1. 1. Enter a full URL or same-origin path and let the page normalise it into a valid HTTP or HTTPS address.
  2. 2. Run a direct browser HEAD request and measure the elapsed time from the start of the request to the response.
  3. 3. Read the status code, reachability signal, and response time together before deciding whether the issue is the target service, browser policy, or your local connection.

Related network resources

Continue with related tools, comparisons, and practical guides.