Website Status Checker
Is it down for everyone or just you? Check up to 20 sites for status, response time and IP.
- Free
- No sign-up
What is a website status checker?
A website status checker answers one question quickly: is this site down for everyone, or just for me? It requests each URL from our server, which is located in Germany (EU), and reports what came back. If the site loads for us but not for you, the problem is likely on your side: your network, DNS, browser cache, VPN or a regional block. If it fails for us too, the site itself is probably having trouble.
You can check up to 20 URLs at once. For each one the tool reports the HTTP status code, the response time measured as time to first byte (TTFB), the final URL after any redirects, whether the TLS certificate is valid, the IP address the hostname resolved to, and the Server header if the site sends one. Each URL gets an up or down verdict with a plain explanation of the status code.
Keep the vantage point in mind. One check from one European location is a strong signal but not a global survey. A site can be reachable from Germany while failing in another region because of a CDN edge problem, a DNS issue with one provider, or geo-blocking. Response times also include the network distance from Europe, so a server in Asia or the Americas will naturally show a higher TTFB here than for local visitors.
How to check if a website is down
- 1
Enter one or more URLs
Paste up to 20 URLs, one per line. Include the specific page if only part of a site seems broken, since a homepage can load while a checkout or API path fails.
- 2
Run the check
Our server requests each URL, follows redirects, validates TLS and records the resolved IP and timing.
- 3
Read the verdict
Check the up or down verdict and the status code explanation. A 2xx after redirects means the site answered normally.
- 4
Compare with your own experience
If we report the site as up but it fails for you, clear your DNS cache, try another network or disable your VPN. If we report it as down, wait a few minutes and check again.
- 5
Inspect the details
Look at the final URL, resolved IP and TLS result. A wrong IP or an invalid certificate often explains failures that look like an outage.
When to use a website status checker
Down for everyone or just me
Before restarting a router or opening a support ticket, find out whether the site responds from an independent server.
Checking your own sites after a deploy
Paste your main URLs after a release or DNS change and confirm every one returns a 200 with a valid certificate.
Monitoring client portfolios
Agencies can paste up to 20 client homepages and spot any that are down, redirecting unexpectedly or serving expired certificates.
Diagnosing slow responses
A high TTFB points to slow server processing, an overloaded origin or a cache miss, rather than heavy images or scripts in the browser.
Verifying DNS cutovers
The resolved IP shows whether our resolver already sees a new host, which helps separate a propagation delay from a genuine outage.
What the status codes mean
2xx codes mean success: 200 OK is the normal answer. 3xx codes are redirects; the tool follows them and reports the final URL, so a 301 to the right page is not a problem. 4xx codes mean the server is up but refused or could not find the request: 403 Forbidden often indicates a firewall or bot protection blocking automated checks, 404 means the page does not exist, and 429 means rate limiting.
5xx codes mean the server or something in front of it failed. 500 is a generic application error, 502 Bad Gateway and 504 Gateway Timeout usually mean a proxy or CDN could not get a valid or timely answer from the origin, and 503 Service Unavailable often signals maintenance or overload. Cloudflare-specific codes in the 520 to 526 range point to problems between Cloudflare and the origin server.
Some failures never produce a status code. A DNS failure means the hostname did not resolve, a connection timeout means nothing answered, and a TLS error means the certificate is invalid, expired or does not match the hostname. These count as down, because browsers cannot load the page either.
Frequently asked questions
Can toolsbox monitor my site and alert me when it goes down?
Yes, with toolsbox Pro. Add a site in the Monitor this site section below the checker and we check it every 1, 2, 3 or 5 minutes from our server. When it stops responding, times out or returns a 5xx or 404 error, we confirm with a second check 10 seconds later and then email you, and email again when it recovers. You also get a response-time chart, 90 days of uptime history and an incident log for up to 20 sites.
Is the website status checker free?
Yes, the website status checker is free with no sign-up. You can check up to 20 URLs per run and see status codes, response times, final URLs, TLS validity, resolved IPs and server headers. Checks are rate-limited per visitor so the service stays fast and cannot be used to flood other sites.
What does the tool request, and is anything stored?
The tool requests only the URLs you enter, plus any redirect targets, from our server in Germany. Results are shown to you and not stored. Requests to private or internal network addresses are blocked, and each visitor is rate-limited. The target site sees one ordinary request per URL.
The tool says the site is up, so why can't I open it?
If the site loads from our server but not for you, the problem is between you and the site. Common causes are stale DNS cached on your device or router, a VPN or corporate firewall, an ISP routing problem, a browser extension, or a regional block. Try another network, such as mobile data, to narrow it down.
Why is the response time higher than I expected?
The response time is measured as time to first byte from our server in Germany, so it includes network distance to the site's server. A site hosted far from Europe will show a higher TTFB here than for nearby visitors. Consistently high values on a nearby server usually indicate slow backend processing or a cache miss.
Why does a site show 403 here but work in my browser?
A 403 for our check but not your browser usually means bot protection is blocking automated requests. CDNs and security plugins often challenge or reject clients that do not run JavaScript or that come from data center IP ranges. The site is up; it is choosing not to answer automated checks.
Can I use this as uptime monitoring?
No, this is an on-demand checker, not a monitoring service. It runs only when you click check, from a single location, and does not send alerts. It is ideal for quick diagnosis after a report or deploy. For continuous monitoring, use a service that checks from multiple regions every minute and notifies you on failure.
Related tools
More Domain & Server tools →Bulk Redirect Chain Checker
Trace every hop for up to 100 URLs — chains, loops, 302s and broken destinations.
Domain & Server
HTTP Headers Checker
See every response header, hop by hop — with a security grade and caching explained.
Domain & Server
DNS Lookup
Query A, AAAA, MX, NS, TXT, SOA and CAA records on Cloudflare and Google DNS — plus SPF and DMARC checks.
Domain & Server
What Is My IP Address
Your public IP, country, browser and connection details — instantly, and never logged.
Domain & Server