⚡ Website Status Checker

Check if any website is online or down, and view response status codes and load times.

Enter Website URL:

💡 Tip: Enter a complete URL and click "Check Status" to verify website availability.

Enter a website URL and click "Check Status" to view results.

The two numbers you get back

Our server makes one real request to the URL you enter and reports the HTTP status code it received and how long the round trip took. The code is the useful half:

200      serving normally
301/302  a redirect - worth following to see where it lands
403      reachable but refused; often a firewall blocking datacentre IPs
429      reachable, rate limited
5xx      the server was reached and the application failed
timeout  no answer at all - DNS, firewall, or genuinely down

The response time covers DNS, the TCP and TLS handshakes and the server's own work, measured from one machine in the eastern United States. It does not include images, stylesheets or JavaScript, so it is not page load time, and it will read higher for a site hosted far from that region.

Getting a useful answer

Check the URL that is actually failing. A homepage on a CDN can be perfectly healthy while the API path behind it is returning 502.
One request from one place is not monitoring. It tells you about this moment. For "is it up over time", run something that polls every minute from several regions.
Repeat before you conclude. A single timeout can be a dropped packet; two in a row from a location that is not yours is worth acting on.

A 200 does not mean the page is correct. An application that renders "database connection failed" still returns 200 unless someone wrote the code to send a 500.

Frequently asked questions

The site opens fine for me - why does this say 403?

Bot protection. Cloudflare, AWS WAF and similar services challenge or block requests from cloud IP ranges, and an automated checker has no browser fingerprint to offer. The site is up; it is declining to talk to us.

Is a 301 a problem?

No - it is what http to https and the www redirect look like. It only matters when the redirects chain through several hops, or when two rules send each other in a circle and the browser gives up.

Why is the response time slower than my browser reports?

Different distance and no cache. Your browser may be reusing a warm connection to a nearby edge node, while this measurement includes a fresh DNS lookup and TLS handshake from a single region.