Website Status Checker
Find out whether a website responds right now: see its HTTP status code, response time and final URL after redirects, for one address or a whole list.
Check History
Is it down for everyone, or just for you?
When a site will not load, the problem may be the site itself, your own connection, DNS or a browser extension. This checker asks the question from somewhere else: a server on Cloudflare's network requests the address and reports what came back. You get a plain Online, Client error or Down verdict, the HTTP status code with its status text, the response time in milliseconds and the final URL after any redirects. It is handy for confirming an outage or a fix, checking that an old address still redirects correctly, or sweeping a list of links after a migration.
How to use the checker
- On the Single Check tab, type an address such as
example.comand press Check or Enter. If you leave out the scheme,https://is added for you. - Read the result card: the coloured verdict, the URL that finally answered, the HTTP status and the response time. If the check could not run, a note explains why (timeout, blocked address, invalid URL and so on).
- The quick-check buttons (Google, GitHub, Cloudflare and others) test a well-known site in one click, a useful control when you suspect your own connection.
- For several addresses, open Batch Check, paste one URL per line (or press Load Samples) and press Check All. Results fill in as they arrive while the progress bar advances.
- Every result is added to Check History; press Clear to empty it.
How the check works
Your browser sends the URL to /api/check, a Cloudflare Pages Function on this site. The function first sends a lightweight HEAD request; if the server answers 405 or 501 (method not supported) or the HEAD request fails, it retries with GET. Redirects are followed by hand, up to five hops, and each new location is checked again so that a public address cannot bounce the request to an internal one. Each request has a 10-second limit. The response time is measured on the server from the first request to the final answer, including DNS lookup, connection setup and redirects.
Status codes are grouped like this:
| Result | Status codes | Typical examples |
|---|---|---|
| Online | 2xx and 3xx | 200 OK, 301 Moved Permanently, 304 Not Modified |
| Client error | 4xx | 403 Forbidden, 404 Not Found, 429 Too Many Requests |
| Down | 5xx, timeout or no connection | 500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable |
One check is a snapshot from a single place: the Cloudflare data centre that handles your request, usually one near you. It says nothing about other regions or about the next five minutes; for alerts and uptime history, use a dedicated monitoring service.
Privacy and limits
The URLs you check are sent to our function, which contacts the target site; the function returns the result and does not save the URL. The target sees a request from Cloudflare, not from your IP address. Your history (the last 50 checks: URL, verdict, time and date) is kept only in this browser's localStorage under the key pingHistory. For safety, the function refuses localhost, private and link-local IP ranges and internal host names, and only http and https are accepted. Batch checks run three URLs at a time.
Frequently asked questions
The site opens in my browser but shows 403 or 503 here. Why?
Many sites put bot protection or firewall rules in front of their servers and treat requests from data-centre networks differently from ordinary visitors. A 403, 429 or 503 in that case means the server is up but declined our request. Try a specific page URL, or confirm from another network.
The checker says Online, but I still cannot open the site.
Then the problem is probably between you and the site: local DNS caching, a VPN or proxy, a firewall, an ISP routing issue or a browser extension. Flushing DNS, trying another browser or switching networks usually narrows it down.
Why does a redirect count as Online?
A 3xx answer means the server is running and pointing somewhere else. The checker follows up to five redirects and shows the final URL, so you can confirm that, for example, the http version lands on https.
Can I check a site on my home or office network?
No. Addresses such as 127.0.0.1, 10.x.x.x, 192.168.x.x and names ending in .local or .internal are blocked, and the server could not reach them anyway. Only publicly reachable http and https sites can be checked.
Why is the response time different from my page load time?
The figure covers a single request and its redirects, measured from Cloudflare's network. A browser also downloads every asset on the page and runs its scripts, which takes much longer.