Website Status Checker

Check whether a website is up right now — reachability, status code, redirect chain, response timing breakdown and total response time.

What is a website status checker?

A website status checker tells you whether a site is up and answering right now. It sends a request to the address you enter and reports the website status in plain terms: whether the server could be reached, the HTTP status code it returned, what that code means, any redirects along the way and how long the response took.

Because the request comes from our server, not your computer, it helps answer the classic question: is the site down for everyone, or just for me?

How the website status check works

If you type a bare domain, the tool adds https:// for you. It then resolves the name, connects to the server and makes a lightweight request that asks only for the response headers, not the full page. Redirects are followed for up to five hops, each connection gets five seconds to open, and the whole check must finish within twelve seconds. Addresses that point to private or internal networks are refused for safety.

The result includes a timing breakdown, the full redirect chain when there is one, and basic server response details such as the content type.

How to check a website's status

Enter a domain or full address, for example example.com or https://example.com/shop.
Press Check Status.
Read the status code and its meaning first.
Check the final URL, the redirect chain and the timing if something looks wrong.

Understanding website status codes

2xx: working

A 200 code means the server answered normally. This is what a healthy page returns.

3xx: redirected

301 and 308 are permanent redirects; 302 and 307 are temporary. The tool follows them and shows where the request ended up.

4xx: a problem with the request

404 means the page was not found, 403 means access was refused, and 429 means the server is limiting how many requests it accepts.

5xx: a problem on the server

Codes such as 500, 502 and 503 mean the website's server, or a service in front of it, failed to handle the request. The fault is on the site's side.

No response at all

If the check cannot connect, resolve the name or finish in time, the result explains which of these happened instead of showing a status code.

When the site is up but not for you

If this check succeeds but the site will not open on your device, the problem is closer to you. Try a private browser window or another browser, switch from Wi-Fi to mobile data, restart your router or clear your device's DNS cache. Company networks and some security software can also block particular websites.

Common uses

Checking whether a site is down for everyone after a visitor complains.
Confirming a site is back after maintenance or a server move.
Seeing which address a link finally lands on.
Getting a quick status code without opening developer tools.

Common problems and fixes

The site works for you but fails here. The server may block automated requests or requests from data centres, or a firewall may only allow certain countries. Check with your host whether such rules are in place.

"Hostname could not be resolved". The domain has no working DNS address record. Check its A record with the DNS Lookup.

405 or another unexpected code. A few servers answer header-only requests differently from normal page loads. If a browser loads the page fine, the site is most likely up.

The request timed out. The server was too slow or unreachable. Try again shortly; repeated timeouts point to an overloaded or offline server.

Related tools

Redirect Checker explains every hop in a redirect chain.
Website Response Time focuses on the timing breakdown.
Bulk URL Status Checker checks up to 15 addresses at once.
DNS Lookup checks the records a site needs to be found.

Frequently asked questions

How do I know if a website is down for everyone?

Run the website status check. The request comes from our server, not your device, so if it succeeds while the site fails for you, the problem is probably your connection, browser or local DNS cache. If it fails here too, the site is likely down or blocking outside requests.

What does HTTP status 200 mean?

Status 200 means OK: the server received the request and answered normally. It is what a healthy, working page returns. A 200 code says the server responded, not that the page content is correct, so a broken page can still return 200.

What is the difference between 301 and 302 redirects?

A 301 is permanent: the content has moved for good, and search engines should index the new address. A 302 is temporary: the original address is expected to come back. Use 301 for site moves and HTTPS upgrades, and 302 for short-term changes such as maintenance pages.

What does a 503 error mean?

Status 503 means Service Unavailable: the server is temporarily unable to handle the request, often because it is overloaded or in maintenance mode. It usually clears on its own. If it lasts, the site owner should check the server load, the hosting account and any maintenance settings.

Why does the status checker say a site is unreachable when it loads for me?

Some sites block automated tools, data-centre addresses or visitors from certain countries, and some only respond on a private network. The site may also be slow enough to pass the time limit. If it loads for you in a browser, it is up, but outside visitors may still have trouble.

Does the status checker load the whole page?

No. It asks the server for the response headers only, which is enough to see the status code, redirects and timing without downloading the page. This keeps checks fast and light. It does not run scripts or load images, so it cannot tell whether the page looks right.

Can I check a specific page rather than the home page?

Yes. Enter the full address, including the path, such as https://example.com/contact. The tool checks exactly that address and follows any redirects from it. This is useful for testing a single page that visitors report as broken while the rest of the site works.