How DeployMonitor checks your site

Request behavior

DeployMonitor sends an HTTP request only to the URL configured for a project. It does not discover links, crawl the full site, index content, or run browser automation.

An uptime result records the HTTP outcome, response time, and any failure reason. Normal checks follow the 5–60 minute interval selected for the project. Failed monitors may be checked more frequently so recovery can be detected promptly.

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

Destination safety

Every initial 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.

Outage confirmation and recovery

Two consecutive failed checks are required before a monitor changes to Down and sends an outage alert. After a confirmed outage, a successful check returns the monitor to Up and can send a recovery alert.

Identify monitoring traffic

DeployMonitor uses this HTTP user-agent:

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

Site operators can match the DeployMonitor token in server logs, firewall rules, or allow lists.

DeployMonitor is a targeted monitoring service and does not consult robots.txt before requesting a configured health URL. Configure monitors only for sites you own or are authorized to operate. To stop authorized checks, disable the project's Uptime Monitor. For an unauthorized check, block the user-agent and contact the account owner responsible for the monitor.