🤖 Overview

Wazzup is a web crawler operated by Wazzup Media GmbH, a German company specializing in website monitoring and analytics. First publicly documented in 2015, the bot is designed to periodically fetch web pages to measure uptime, response times, and detect content changes for clients subscribed to the Wazzup monitoring service. It serves as a non-malicious agent that provides critical infrastructure health data.

🌐 Technical Behavior

The Wazzup bot performs HTTP GET requests at configurable intervals, typically ranging from 1 to 60 minutes depending on the monitoring plan. It follows standard HTTP protocols and supports both IPv4 and IPv6. The bot’s IP addresses are primarily sourced from Amazon Web Services (AWS) and Hetzner data centers in Europe and North America. Requests include a unique identifier in the X-Wazzup-Check-ID header for traceability. The crawler does not follow JavaScript redirects or execute client-side scripts; it only fetches the raw HTML and headers. It also respects Cache-Control headers to avoid stale data.

📋 robots.txt Compliance

Based on official documentation from Wazzup.io, the bot fully complies with the Robots Exclusion Standard. It reads robots.txt at the start of each crawl session and will not access any path disallowed by the Disallow directive. However, it does not honor Crawl-Delay directives as its crawl interval is predetermined by the monitoring schedule.

🔍 Detection Indicators

The primary User-Agent string is Wazzup/1.0 (+https://wazzup.io/bot). Secondary identifiers include the X-Wazzup-Bot header set to true and a User-Agent that may contain the version number, e.g., Mozilla/5.0 (compatible; Wazzup/2.0; +https://wazzup.io). The bot does not mimic common browser user-agents. Network administrators can also identify the bot by its consistent usage of AWS IP ranges listed in the ip-ranges.json file for the eu-central-1 region.

📊 Data Usage

Collected data is aggregated into Wazzup’s dashboard to display uptime percentages, response time trends, and content integrity alerts. Historical data is stored for up to 90 days for subscribers. The bot does not index or store content beyond the last modified response; it only records HTTP status codes, headers, and body size. No personal data is collected unless explicitly exposed in the response body (e.g., in error messages), which is then hashed for anomaly detection.

⚙️ Rate Limiting Policy

Rate-limiting is justified because the Wazzup bot may generate frequent requests (up to once per minute) for high-priority monitors, which could impact server resources if unconstrained. It is recommended to allow the bot with a rate limit of 10 requests per minute per IP to ensure monitoring accuracy while preventing abuse. Blocking the bot entirely would degrade service for legitimate uptime monitoring, so threshold-based throttling is the preferred policy.

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the bots listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.