Is it down?
Check whether a website is up or down right now. We make a single live request to it and report back the result - nothing is saved.
A single failed request rarely means a site is actually down for everyone - it could be a local network issue, a DNS problem on your end, or a temporary blip that's already resolved. This tool makes one live request from our servers and shows you the raw HTTP status code and response time, so you can tell the difference between "down for me" and "down for everyone" before you panic or open a support ticket.
For a site you check often, a single manual check isn't enough - you won't know it went down at 3am unless someone's watching. Kawze checks your endpoints on a schedule and alerts you by email or SMS the moment something breaks.
Frequently asked questions
Why does this say a site is up when it's down for me?
We check from our own servers, not your network. If a site is unreachable only from your location, the problem is likely your ISP, DNS, VPN, or a regional outage rather than the site itself.
Does this check store or log the URLs I check?
No. Each check is a single live request made on demand - nothing is saved or associated with your account.
What HTTP status codes count as "up"?
Any response in the 2xx or 3xx range is treated as up. Most 4xx and 5xx status codes, timeouts, and connection errors are treated as down. A 403 response is flagged as a possible issue rather than down, since it usually means the site's own bot protection blocked our request rather than the site being unreachable.
How is this different from Kawze's uptime monitoring?
This tool is a one-off manual check. Kawze's monitoring runs checks continuously on a schedule and alerts you automatically the moment a monitor goes down.