Monitoring bot

DeployMonitor Bot

DeployMonitor operates an availability monitoring bot that checks customer-configured HTTP and HTTPS endpoints for uptime, response status, response time, redirects, and TLS certificate health.

Frequently asked questions

DeployMonitor requests customer-configured monitor URLs, their redirects, and the robots.txt files needed to check access rules. It does not discover links, index content, execute arbitrary browser automation, or crawl an entire site.

The bot sends an HTTP request to the configured monitor URL, records the response code and response time, and can optionally verify that expected response text is present.

User-agent

DeployMonitor identifies availability checks with a dedicated user-agent token. Site operators can use this token in logs, WAF rules, or allow lists.

HTTP User-Agent header

Mozilla/5.0 (compatible; DeployMonitor/1.0; +https://deploymonitor.com/bot)

Copy HTTP User-Agent header

Match pattern

DeployMonitor

Copy match pattern

Robots.txt and opt-out

DeployMonitor respects robots.txt before requesting a configured uptime URL or following a health-check redirect. Rules are evaluated for DeployMonitor, with wildcard rules used when no matching bot group exists.

Policies are cached for 12 hours per origin (scheme, host, and port), so rule changes can take up to 12 hours to apply. A 404 or other 4xx response means no restrictions. On a 5xx response or network failure, checks are skipped unless a valid cached policy is available. Skipped checks do not record downtime or trigger outage alerts.

These rules govern HTTP uptime checks. TLS certificate and domain registration checks run separately.

Allow monitoring

User-agent: DeployMonitor
Allow: /

Copy allow monitoring example

Block all uptime checks

User-agent: DeployMonitor
Disallow: /

Copy block monitoring example

Allow a health path

User-agent: DeployMonitor
Disallow: /
Allow: /health

Copy health path example