HTTP, ping, TCP, DNS, or straight against a JSON API — each protocol checks what actually matters for that kind of service. Response codes and expected keywords are configurable per monitor.
HTTP(S) for a site, TCP for a service port, ping for a raw server, or a JSON request for an API.
Accepted response codes, expected keyword in the response body — not just "it responds", "it responds correctly".
Email and Discord, with configurable escalation and anti-spam cooldown to keep the noise down.
Configurable response codes — an expected 404 or 500 won't trigger a false alert.
Checks that a specific keyword appears in the response — catches a page that returns 200 but shows an application error.
Raw network availability, no HTTP involved — for a mail server, a database, an internal service.