DeployMonitor

Monitoring

How DeployMonitor checks your site

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

Request behavior

An uptime result can record the HTTP outcome, response time, and failure reason. Normal checks follow the project's 5–60 minute interval. Failed monitors may be checked more frequently to confirm an outage and detect recovery.

The connection and response timeout is 10 seconds. Redirects are followed one at a time, with a maximum of five redirects.

Destination safety

Every initial URL, robots.txt URL, and redirect destination must be a public HTTP or HTTPS endpoint. DeployMonitor rejects:

  • Localhost and private-network destinations.

  • Loopback, link-local, reserved, multicast, documentation, carrier-grade NAT, and cloud metadata address ranges.

  • URLs containing embedded usernames or passwords.

  • Hosts that cannot be resolved publicly.

  • Redirects to blocked destinations.

This validation also applies when a project URL is created or changed.

Robots.txt behavior

Before requesting an uptime URL or following a health-check redirect, DeployMonitor reads the applicable robots.txt policy for the DeployMonitor user-agent. Wildcard rules are used when there is no matching bot group.

Policies are cached for 12 hours per origin, where the scheme, host, and port identify the origin. A 404 or other 4xx response means there are no restrictions. A 5xx response or network failure pauses the check unless a valid cached policy is available.

When a rule blocks the URL, or the policy is temporarily unavailable, DeployMonitor skips the uptime check. A skipped check does not create a failed result, count as downtime, advance outage confirmation, or send an outage alert. The project's Settings > Monitoring page shows the reason, and checks resume automatically when the policy permits them.

Use one of these rules when appropriate:

User-agent: DeployMonitor
Allow: /

User-agent: DeployMonitor
Disallow: /

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

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

Identify monitoring traffic

DeployMonitor uses this HTTP user-agent:

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

Site operators can match the DeployMonitor token in server logs, firewall rules, or allow lists. The public bot page also provides the current identification details and IP list.

Configure monitors only for sites you own or are authorized to operate. To stop authorized checks, disable Uptime Monitor under Settings > Monitoring. For unauthorized monitoring, block the user-agent and contact [email protected].