Uptime
Use Uptime monitors for HTTP and HTTPS availability checks. They validate whether a URL responds, whether the response status matches expectations, and how long the response took.
Keyword
Use Keyword monitors when a page must contain or must not contain specific text. This is useful for content regressions, landing page validation, stock or availability text, and simple business-critical page checks.
TLS
Use TLS monitors for certificate validity and expiry awareness. TLS checks are intentionally lower-cadence than normal uptime checks because certificate state changes much less frequently.
Heartbeat
Use Heartbeat monitors for cron jobs and scheduled tasks. Your job calls a Watchfox heartbeat URL; Watchfox alerts when the expected ping is missing.
Sitemap
Use Sitemap monitors for light sitemap validation and broken-link detection within sitemap scope. Sitemap checks are useful for finding obvious crawl and URL health problems.
Domain
Use Domain monitors for domain expiry risk. Domain data can be source-limited depending on registry and RDAP availability, so unknown states should be investigated rather than treated as confirmed outages.
Probe coverage
For Uptime and Keyword monitors, Watchfox chooses the primary scheduled probe group automatically. The setup UI does not ask you to choose P1/P2/P3 because these are internal compatibility labels, not customer-visible location choices.
Normal scheduled checks use 1 primary probe group. On Agency and Pro, smart outage verification may use additional probe coverage automatically when a failure is detected.
Recent check evidence can still show neutral Probe group ... labels to describe which internal probe group produced a historical check result.