Monitors

Monitor types

Website, API, keyword, ping, DNS, and heartbeat checks explained.

Website: Requests an HTTP or HTTPS URL and expects a configurable status code (default 200). Response time feeds the degraded threshold.
API: Like a website check with more control: choose the HTTP method (GET, HEAD, POST, PUT, PATCH, DELETE), send a request body, and optionally assert that the response contains a string, for example "database":"ok".
Keyword: Fetches a page and asserts that a text snippet (up to 200 characters) is present, or absent. Useful for detecting error pages that still return 200.
Ping: Opens a TCP connection to host:port (default port 443). Success means the socket opened; response time is the connect latency. Works for anything TCP: databases, mail servers, game servers.
DNS: Resolves a record (A, AAAA, CNAME, MX, TXT, or NS) and optionally asserts the answer contains an expected value. Catches expired zones and hijacked records.
Heartbeat: Push instead of pull: your cron job or worker pings a unique URL on every run, and the monitor goes down when pings stop. See Heartbeat monitors.

SSL certificate and domain expiry are add-ons you enable on any monitor rather than separate monitor types. See SSL & domain expiry.