Skip to content

Server Status & HTTP Reachability Checker

Check whether a site is reachable from this server: DNS resolution, TCP connection, HTTP response code and latency. Results cached for two minutes.

sensors

Server Status & HTTP Reachability Checker

Audit DNS resolution, TCP connectivity, HTTP response codes, latency, and TLS availability in real time.

What this tool does

Enter a host name or URL and the tool runs a short series of checks from this site’s server: does the name resolve in DNS, can it connect, what HTTP code comes back, and how long does it take. The result is a quick answer to “is it down for everyone, or just for me?”

Reading the result

  • DNS failed: the name doesn’t resolve. Check your DNS records and name servers.
  • Connected but a 5xx code: the server is reachable and the web application is failing.
  • Connection timeout: the host is down, a firewall is dropping traffic, or the port is closed.
  • Slow response: look at the latency. A single slow reading is not a verdict, so run it a few times.

What it can’t tell you

One check from one place is a small sample. A site can be reachable from this server and blocked in your country, or the other way round. It is not uptime monitoring either: it checks right now and keeps nothing. If you need alerts, use a monitoring service that checks every minute from several regions.

Some sites also block requests from server networks, so a 403 or a timeout doesn’t always mean the site is down.

Cache notice

Results are cached for two minutes. If you restart a service and check again straight away, you may see the earlier result. Wait two minutes for a fresh check. Up to 15 checks a minute are allowed.

For a detailed look at the response, see HTTP Status Code Checker and HTTP Headers Checker.

Does this monitor my site over time?

No. It makes a single check when you press the button. For alerts, use an uptime monitoring service.

The tool says it can’t connect, but my site works for me. Why?

This server’s network may be blocked by a firewall or bot protection, or there may be a regional issue. Try again later or from another tool.

Why does it show the same result after I fixed the problem?

Results are cached for two minutes.

Does it test HTTPS certificates?

It reports TLS availability, but for certificate details use the SSL Certificate Checker.

What checks does it run?

It resolves the name in DNS, tries to connect, requests the page and reports the HTTP status code and how long it took.