HTTP (Website) Monitor
The classic uptime monitor: we call your URL on a schedule and alert you the moment it stops answering correctly.
An HTTP monitor is the core of any uptime monitoring setup. Give Kawze a URL and we act as an uptime monitor for it - calling it on a schedule from our monitoring infrastructure, checking the response against rules you define, and alerting your team the instant something looks wrong. It works as a simple website uptime monitor for a marketing page, or as a full API uptime monitor with custom methods, headers, a request body, and authentication for a login form or REST endpoint.
How this uptime monitor works
- Add the URL you want this uptime monitor to call, and pick an HTTP method - GET, POST, PUT, PATCH, DELETE, or HEAD.
- Optionally attach a request body (JSON or form-urlencoded) for methods that support one, custom headers, and basic or bearer-token authentication.
- Set the status codes that count as "up" - an exact code like 200, or a whole class like 2xx or 3xx - and optionally require (or forbid) a keyword in the response body.
- Choose a check interval; the monitor calls your URL on that schedule and logs status code, response time, and any failure reason.
- A run of consecutive failures triggers an alert by email or SMS to whichever team members you choose, plus a recovery alert the moment it clears.
HTTP (Website) Monitor features
Every feature this monitor supports, and which plan it's included on.
All HTTP methods
FreeGET, POST, PUT, PATCH, DELETE, and HEAD - so this monitor covers plain pages as well as REST API endpoints.
Custom request body
FreeJSON or application/x-www-form-urlencoded bodies for POST/PUT/PATCH requests.
Custom headers
FreeSend any headers your endpoint needs - API keys, content type, anything.
Authentication
FreeBasic auth (username/password) or a bearer token, sent with every check.
Status code matching
FreeAccept an exact code (200, 301) or a whole class (2xx, 3xx) as "up".
Keyword matching
FreeFail the check if the response body is missing an expected keyword, or contains one it shouldn't - catches soft failures a 200 status code alone would miss.
Follow redirects
FreeToggle whether the monitor follows a redirect chain or treats a redirect as the final response.
Cache breaking
FreeAppends a timestamp query parameter to every check so a CDN or reverse proxy cache can't hide a real outage behind a stale cached response.
Custom user agent
FreeOverride the default Kawze user agent, useful if a site blocks or challenges unrecognized bots.
Configurable timeout
FreeSet how long to wait for a response, from 1 to 60 seconds, before the check counts as failed.
Tags and groups
FreeOrganize monitors by tag or group them by service.
Email and SMS alerts
FreePer team member, per status (up/down), open and recovery alerts on every channel.
Webhooks and Slack alerts
FreeSend outgoing webhooks to any URL, or wire this monitor into Slack.
10-second check interval
Max+The fastest available interval for this monitor, for when every second of downtime matters.
30-second check interval
Mid+A faster interval than the default 5-minute floor.
What's free and what's paywalled
- Every HTTP method, status code rule, header, authentication type, keyword match, and alert channel is available on every plan, including Free - Kawze doesn't paywall the core functionality of this uptime monitor.
- What scales with plan is check frequency and monitor count: Free and Entry run every website monitor at a 5-minute interval, Mid unlocks 30 seconds, and Max unlocks 10 seconds.
- Monitor limits: 5 on Free, 50 on Entry, 150 on Mid, 300 on Max - all under one account with unlimited team members, so adding teammates never costs extra.
- SMS alerts are metered by monthly credit allowance per tier (Free has none included but credits are purchasable); email alerts are unlimited above Free's daily cap.
Frequently asked questions
Is the HTTP uptime monitor free?
Yes. Kawze's Free plan includes 5 monitors with full access to every HTTP method, header, authentication type, status code rule, and keyword match - the core uptime monitor functionality is never paywalled. Free and Entry run checks every 5 minutes; Mid and Max unlock faster intervals.
Can this uptime monitor check an API, not just a web page?
Yes. Set any HTTP method, custom headers, a JSON or form-urlencoded body, and basic or bearer-token authentication, so the same monitor type covers a marketing page, a login form, or a JSON API endpoint.
What counts as "down" for this monitor?
You define it: an unexpected status code, a timeout, a connection failure, or a missing/unwanted keyword in the response body. Kawze only alerts after a run of consecutive failures, so a single blip doesn't trigger a false alarm.
How fast can this monitor check my site?
Down to every 10 seconds on the Max plan, every 30 seconds on Mid, and every 5 minutes on Free and Entry.