Website availability check

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.

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.

• 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.

CORS, TLS, DNS, extensions, browser policy, target handling of HEAD requests, and redirect blocking can affect the result. A completed opaque response does not expose the HTTP status, while a failed fetch does not prove the target is offline.

• 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.