It works here but my users say it is down — why?

It may be a regional network problem, DNS that has not propagated, a firewall on their side, or a site that only serves some regions. Compare resolvers with the propagation checker and ask users for the exact error they see.

Can I use the response time as a performance metric?

Only as a rough indication. It is a single measurement from one location, includes network round-trip time, and excludes page resource loading and browser rendering. For real user experience, use real user monitoring or a multi-location performance test.

NETWORK TOOLS · QUERIED BY OUR SERVER

Website Status Checker

Check whether a URL currently responds, showing the status code, response time, and any redirects.

This lookup is made by our server contacting the host, not by your browser.

About this tool

Enter a URL to see whether the site responds, what status code it returns, how long it took, and whether it redirected. Among status codes, 2xx is success, 3xx is a redirect, 4xx means the request was at fault (404 not found, 403 refused), and 5xx means the server failed. The response time covers DNS resolution, TCP connection, TLS handshake, and waiting for the first byte, and depends heavily on network conditions at the measuring location — good for answering 'is it responding' and 'is it obviously slow', not for benchmarking. It is a single measurement from a single point: reachable here does not mean reachable everywhere, and the reverse is equally true.

How it works

Enter the URL to check.
Review the status code, response time, and redirect chain.
Use a dedicated monitoring service if you need continuous checks.

Limits and notes

One request from one location. It reports the status code and the time from sending to first response. This is not global availability and is not a substitute for continuous monitoring.

How your input is handled

The domain or URL you enter is sent to our server, where an isolated process contacts the host on your behalf. Nothing you submit is stored or written to an analytics event, no cookies or authorization headers are forwarded, and the target's JavaScript is never executed. The server may only reach publicly routable internet addresses; private ranges, loopback, and cloud metadata addresses are refused.

Frequently asked questions

It works here but my users say it is down — why?: It may be a regional network problem, DNS that has not propagated, a firewall on their side, or a site that only serves some regions. Compare resolvers with the propagation checker and ask users for the exact error they see.
Can I use the response time as a performance metric?: Only as a rough indication. It is a single measurement from one location, includes network round-trip time, and excludes page resource loading and browser rendering. For real user experience, use real user monitoring or a multi-location performance test.

← All network tools