Website availability check
Estimate whether a browser request completes and how long it takes
This sends an HTTPS HEAD request from your browser. The destination receives your IP address and request headers. Redirects are blocked. This is not ICMP ping.
Target + results
Enter an HTTPS website address or IP address. If you omit the scheme, the tool adds
https://. What this check does
Traditional ping sends ICMP echo packets. Browsers cannot do that, so this page sends one direct HTTPS HEAD request and measures how long the browser takes to complete or reject the fetch.
When this check helps
This browser check can show whether a request completes from your current browser context. It cannot replace ICMP ping or independent uptime monitoring.
- Checking browser access: see whether a request can complete from this page.
- Troubleshooting: capture a quick signal before using deeper network tools.
- Measuring one attempt: record elapsed time for one browser request, not network latency.
- No software installation: run checks directly from your browser.
Understanding results
- Target: the URL or IP address that was tested.
- Status: indicates whether the browser fetch completed.
- Elapsed request time: time from starting fetch until its promise completes or rejects. It includes browser, connection, TLS, server, and policy work.
- Timestamp: the UTC time when the test ran.
- Error details: the browser error; it may not identify the server's actual status.
Limitations
CORS, TLS, DNS, extensions, browser rules, HEAD request handling and blocked redirects can affect the result. The browser may receive a response without exposing its HTTP status. If the request fails, try opening the site directly; it may still be online.
Common Use Cases
- See whether one HTTPS request completes from this browser.
- Capture an elapsed-time signal before deeper diagnostics.
- Compare browser behavior across two known test endpoints.
- Reproduce a CORS, TLS, or browser-policy failure.