# RADAR Monitor for Cloudflare-Protected Targets

> MazeBolt Verified Bot Monitor: How to Identify and Verify

Part of the [MazeBolt Help Center](https://support.mazebolt.com/) › [FAQs](https://support.mazebolt.com/faqs). Updated 2026-11-16. HTML page: https://support.mazebolt.com/faqs/radar-monitor-for-cloudflare-protected-targets

---

RADAR checks that an organization’s DDoS protection is effective in action, without disrupting production. To do this safely, RADAR uses a monitor to confirm that the customer’s Target stays responsive. If monitoring traffic is blocked, RADAR is unable to validate the Target’s availability. This page explains how to identify and verify the RADAR monitor.

## Why RADAR Uses Monitors

RADAR runs DDoS simulations against live production environments, it must always know how the Target is responding. Before a simulation starts, the monitor measures the Target’s normal response time and uses it as a baseline. During the simulation, it keeps tracking the Target’s responsiveness. If the response time deviates from the expected range, RADAR stops the simulation automatically. This is how RADAR keeps every test nondisruptive to the customer’s service. RADAR supports several monitor types for different kinds of services.

For Targets protected by Cloudflare, RADAR uses only dedicated monitors, operated directly by MazeBolt. It sends requests only to Targets that a RADAR customer has added to their own environment, and only after domain ownership has been verified and contractual authorization is in place. Each check is a single HTTPS GET request, sent to the URL configured for the Target on the MazeBolt platform. The monitor measures the time it takes to receive a response. Each request includes a `_Mazebolt=<timestamp>` query parameter, which makes every request unique so that the response comes from the origin server and not from a cache.

## How to Identify and Verify the Monitor

- **User-Agent**: MazeBolt Verified Bot Monitor
- **Request:** HTTP GET to the Target’s configured URL, with a `_Mazebolt=<timestamp>` query parameter.
- **Headers**: Every request is signed using Web Bot Auth and includes the Signature, Signature-Input, and Signature-Agent headers.
- **Signature-Agent**: Each request’s signature can be verified against the public keys published in MazeBolt’s key directory: webbotauth.ops-boltlabs.com
- Requests that claim to be the RADAR monitor but fail these checks do not come from MazeBolt.
- **Rate**: The monitor sends traffic in two scenarios: routine monitoring, at one request every 15 seconds, and during a simulation, at two requests per second. These rates apply per monitoring node.

## Data Use

The monitor records only the response time of each request.

The response body is never stored, indexed, or cached. No data is Collected data or used for any purpose other than showing the customer their Target’s availability.
