Kawze Uptime Bot

You're here because a request from our monitoring bot hit your server. Here's what it is, why it's checking your site, and how to allow or block it.

What this is

Kawze is an uptime monitoring service. Customers configure checks against their own URLs, and our infrastructure polls those URLs on a schedule (typically every 30 seconds to a few minutes, depending on the customer's plan) to confirm they're up and responding as expected.

If you're seeing this page, a Kawze customer has set up a monitor pointed at your domain - either because they own it, or because it's a dependency their service relies on.

User-Agent string

Requests from our monitoring bot identify themselves with this User-Agent header:

Kawze-Uptime/1.0 (+https://kawze.com/uptime-bot)

Customers can optionally override this with a custom User-Agent of their own choosing for their specific monitor, so not every request against your server described as "Kawze" will necessarily carry this exact string.

Request behaviour

Requests from the bot generally look like this:

  • HTTP methods: GET, HEAD, POST, PUT, PATCH, or DELETE - configured per monitor.
  • Standard TCP/TLS connections, no port scanning or protocol probing.
  • No JavaScript execution - we make a single request and read the response.
  • Requests carry a short timeout (customer-configured, typically 5–60 seconds).
  • Some monitors append a ?t=<timestamp> query parameter to defeat caching (CDNs, browser caches, reverse proxies) so a stale cached response can't mask a real outage.
  • We do not follow links, crawl your site, or submit forms beyond the single configured endpoint.

Respecting robots.txt and rate limits

Because each monitor checks exactly one URL its customer configured, the bot does not crawl or discover pages, so robots.txt disallow rules generally aren't applicable in the way they are for search engine crawlers. That said, we keep request volume low and predictable - one request per monitor per interval, no bursts or retries beyond a single reasonable retry on transient network failure.

If our traffic is causing you a problem, please get in touch (details below) before blocking us - we're happy to work with you directly.

Allowlisting

If you'd like to explicitly allow our checks (for example, past a WAF or bot-management rule), the most reliable way is to allowlist requests matching the User-Agent above. We don't currently publish a fixed IP range, as checks may run from infrastructure that changes over time.

Blocking this bot

If you'd prefer we not check your site, you're welcome to block requests matching our User-Agent at your firewall, WAF, or web server config. Note that if a Kawze customer has configured a monitor against your domain, blocking us will simply cause their check to report your site as down - so it may be worth first checking whether that's a monitor you're happy to have removed, using the contact details below.

Contact

Questions, concerns, or requests relating to bot traffic can be sent to [email protected], or reported directly via our abuse reporting form.