Is it down, or is it just you? Enter a URL and we load it from our servers right now and tell you whether the site is up.
Free, no login, no email. Nothing stored: every check is a fresh request. Markdown copy · API and MCP
Enter any address
A bare domain or a full URL with a path. We check the exact page you give us, so a broken checkout page shows as down even when the homepage is fine.
We request it live
Our server loads the page the moment you ask, following redirects the way a browser would. Nothing is cached: an answer from this morning is the wrong answer during an outage.
Get a clear answer
Up or down in the largest type on the page, with the HTTP status, the response time, where any redirect landed, and the exact time of the check. The result has its own link you can send to whoever needs to see it.
When a site will not load, the first question is never what broke. It is whose problem it is. A page that fails in your browser can be failing because the server is gone, or because your office DNS resolver is stale, your VPN is routing through a region the site blocks, a browser extension is rewriting the request, or the site simply rate limited your address after a few refreshes. Every one of those looks identical from a single chair: a spinner, then an error.
So this tool does the one thing that separates them. It asks the site from somewhere that is not you. Our server makes a plain request, the way a first-time visitor's browser would, and reports what it saw. If we get an answer and you do not, the fix is on your side of the connection, and you can stop refreshing. If neither of us gets one, it is the site, and someone with access needs to know.
Most status checkers call anything that is not a 200 a failure. We do not, because the question is whether the server is alive, not whether it liked our request. A 403 from a bot blocker, a 401 from a login wall, a 404 for a page that moved: each of those is a server that is running, answering, and making a decision. We show you the status so you can judge it, and we reserve the word down for the cases where nothing answered at all, or the server answered that it was broken.
This is a snapshot from one place at one moment. A site that flaps during a deploy can be up for us and down for you ten seconds later. A site that blocks a region is up from here and down from there. Run it twice if the first answer surprises you, and treat a verdict that changes between runs as its own finding: unstable is a different problem from down, and usually a more urgent one.
Up means the server answered with any HTTP status below 500. That includes a 403 or a 404: bot protection and a missing page are not outages, the server is clearly there, and we show the status so you can judge. Down means a 5xx server error, no answer within 10 seconds, a refused connection, a domain that does not resolve, or a redirect chain that never landed.
The same run this page does, as an HTTP endpoint and as the MCP tool check_website_status. No account, no API key. Full reference.
curl -sS https://usesuperflow.ai/api/tools/website-status-checker \
-H 'Content-Type: application/json' \
-d '{"url":"example.com"}'Returns { verdict: 'up' | 'down', reason?, httpStatus?, responseTimeMs, requestedUrl, finalUrl, redirectCount, checkedAt, submittedUrl }. 60 runs per hour per IP. Allow up to 30 seconds.
claude mcp add --transport http superflow https://usesuperflow.ai/api/mcpThen ask your agent for check_website_status. Setup for Claude Desktop, Cursor and VS Code is on the reference page.
No login, no email, no ads. Same as this one.
Superflow agents open every page of every site you ship, on every change, and check them against your own QA rules. They tell you when something breaks, changes, or quietly stops working, not only when the whole site goes dark.