Website Down Checker
This free website down checker opens a web address from our servers and tells you whether it is up, answering with an error, too slow, or not found in DNS at all. It shows the status code, how long the answer took and any redirects on the way.
The check runs on our servers, so your browser only talks to tpc-hosting.com. We look up the address in DNS, then open the page once, the way a visitor would, and keep nothing.
Free, no signup. Try it with github.com.
What this check does
First we look up the domain in DNS, to see whether it has an address at all. If it has none, the site cannot be reached by anyone, and we tell you the domain does not resolve. Otherwise we open the page once, from Cloudflare's network, the way a visitor would, and follow up to five redirects.
If you typed only a domain, we try https first. If that cannot connect, we try plain http once before calling the site down. We give up on a slow site after 10 seconds. We then read only the status line and headers, not the page itself, and keep nothing.
The check runs from one place, a Cloudflare location that the result names. A site that is down in one country or network while fine elsewhere can still look up here, so treat the answer as a strong hint, not proof of what every visitor sees.
How to read the result
Up means the site answered with a normal status, like 200 OK, and the result shows how fast. It can still feel slow to you if your own connection is the weak link.
An error means the server answered but with a status of 400 or higher. A 5xx code such as 500, 502 or 503 points to a problem on the server. A 404 means that exact page is missing. A 403 or 429 can mean the site turned us away on purpose, because some sites block automated checks.
Down means we could not connect at all, and too slow means nothing came back within 10 seconds. Does not resolve means the domain has no IP address in DNS, which usually points to an expired domain, a missing record or wrong nameservers.
It loads for them but not for me
If the checker says the site is up and you still cannot open it, the problem is probably on your side. The usual causes are a stale browser cache, an old DNS answer on your computer, a VPN or proxy, a firewall or antivirus, or your internet provider. The result lists what to try, in order.
A quick test is to open the site on your phone using mobile data. If it loads there, your home or office network is the cause, not the website.
What to do if it is your own site
Start with the kind of failure. Does not resolve points to the domain and its DNS records. Down or too slow points to the server, its firewall or its load. An error status points to the website software, so check the error log first.
From there, use the dig tool to see what your domain points to, the DNS propagation checker after a DNS change, the SSL checker if visitors see a certificate warning, and the redirect checker if the page loops. If your server keeps going down or running out of resources, it may be time to move to a plan with more room to grow.
Frequently asked questions
Is the website down for everyone or just me?
This tool opens the site from our servers, not from your computer. If it answers there, the site is working and the problem is probably on your side: your browser, network, VPN or internet provider. If it fails here too, the site is very likely down for others as well.
Do you check from several locations?
No. Every check runs from one Cloudflare location, and the result tells you which. A site that is blocked or broken only in some countries or networks can look fine here, so a positive result does not prove that every visitor can get in.
What does "doesn't resolve" mean?
The domain has no IP address in DNS, so no browser can find the server. Common causes are an expired or unregistered domain, a deleted DNS record, or nameservers that are wrong or not answering. Check the records with the dig tool.
Why does it say the site has an error when it opens for me?
Some sites answer automated checks differently from browsers. A firewall or bot protection can send us a 403 or 429 while real visitors get the page. If you can open the site and we see an error, the site may be blocking checkers like this one.
Why did the check take 10 seconds and then fail?
We wait up to 10 seconds for a site to answer. If nothing comes back in that time, we report it as too slow. That usually means an overloaded or frozen server, or a firewall that silently drops connections.
Do you check http as well as https?
If you type only a domain, we try https first and then plain http once if https cannot connect. If you type the full address with http:// or https://, we check exactly that one.
Can I check any website?
You can check any public website by its domain name. We do not check IP addresses, private or local names, other ports or tpc-hosting.com itself, and we follow redirects only to other public sites.
Do you store the addresses I check?
No. We look up the address, open it once and show you the result. We do not keep a list of what was checked.
Dig deeper
Redirect Checker
Follows a URL hop by hop to its final page: status codes, timing, loops and long chains.
Trace redirectsDNS Propagation Checker
Just changed a record? Ask 6 public resolvers at once and see side by side who already has the new answer.
Check propagationSSL Checker
Checks a site's certificate, chain, expiry date and TLS versions, and explains what's wrong in plain English.
Check a certificate