Website Status Checker

Website Status Checker

Enter a domain and click Check Status. Our server requests the site the same way a browser does and shows the HTTP status code it gets back. For google.com that's 200 OK: the site is up and serving pages.

Is it down for everyone, or just you?

Compare what the checker sees with what you see.

The checker says it's up, but it won't load for you. The problem is on your side. Common causes:

• Your Wi-Fi or ISP.
• Your device's DNS cache still pointing at an old IP after a hosting move.
• A VPN, firewall or browser extension.
• An old entry in your hosts file.

Try the site on mobile data. If it loads there, it's your network. Flushing your DNS (ipconfig /flushdns on Windows) fixes the cached-IP case.

The checker shows an error, but the site loads for you. You may be looking at a copy cached by your browser or a CDN. Or the site may block automated requests and data-center IPs, which is common with bot protection. In that case real visitors are fine.

Both fail. It's the site. The status code tells you what kind of failure it is.

What the status codes mean

200: OK

The server returned the page. That doesn't guarantee the page looks right. A blank page or one full of PHP warnings can still come back as 200.

3xx: Redirects

• 301: moved permanently.
• 302: moved temporarily.
• 307 and 308: stricter versions of 302 and 301.

When a domain redirects (google.com sends you to www.google.com, for example), the checker follows the redirect and reports the status of the page it lands on. To see every step in between, use the Redirect Checker.

4xx: The request was refused or the page doesn't exist

403 Forbidden. The server refused the request. Wrong file permissions or a security plugin are common causes. So is a firewall blocking our checker specifically. If you get a 403 here but the site works in your browser, visitors are probably fine.

404 Not Found. The server is up, but there's nothing at that address. On a single page that usually means a broken link. On a homepage it usually means the server is pointing at the wrong folder.

410 Gone. The page was removed on purpose.

429 Too Many Requests. The site is rate-limiting. It may have seen too many requests from our checker.

5xx: The server or application failed

500 Internal Server Error. The application crashed. It often happens right after a plugin or theme update, a PHP version change or an edit to .htaccess. Your server's error log names the actual cause.

502 Bad Gateway. The web server is running, but the application behind it (PHP-FPM or a Node.js process, for example) didn't answer properly. Usually that process crashed or needs a restart.

503 Service Unavailable. The server is overloaded or in maintenance mode. WordPress returns 503 while it installs updates. If an update fails halfway, the site can get stuck in maintenance mode. Deleting the .maintenance file in the site's root folder fixes it.

504 Gateway Timeout. The application took too long to respond. That usually points to a slow database query or an overloaded server.

Cloudflare's own errors (52x)

Sites behind Cloudflare have their own set of codes. Each one means Cloudflare is working but couldn't get a proper answer from your server:

Downtime and SEO

A short outage won't hurt your rankings. Googlebot simply tries again later.

For planned maintenance, return a 503 status, ideally with a Retry-After header. Avoid serving a normal 200 page that says "back soon," because that tells search engines the maintenance message is your content.

What does cause damage is errors lasting more than a day or two. Google slows its crawling and can start dropping pages from its index.

A one-off check isn't monitoring

This tool answers "is it up right now?" To find out that your site went down at 3 a.m., you need an uptime monitoring service that checks every minute or two and alerts you.

FAQ

Is this the same as a ping?

No. Ping tests whether a server answers at the network level. Many servers ignore ping while serving websites perfectly, and a server can answer ping while the website on it is broken. This tool checks the website itself. For a network-level test, use Ping.

Can I check a specific page instead of the whole domain?

Use the HTTP Status Code Checker for exact URLs like a single blog post or product page.

What does "too many redirects" mean?

The site is redirecting in a loop. A classic cause is Cloudflare's "Flexible" SSL mode combined with a server that forces HTTPS. Cloudflare connects to the server over HTTP, the server redirects to HTTPS, and Cloudflare connects over HTTP again, forever. Switching Cloudflare to "Full" mode usually fixes it.

The site doesn't respond at all. Where do I start?

No status code at all is a different failure from an error code. Check three things:

1. DNS: use DNS Lookup to confirm the domain points to the right server.
2. The server: confirm it's actually running.
3. The certificate: use the SSL Checker, because an expired certificate can stop connections completely.