| HTTP / HTTPS | Response code, response time and a keyword in the body — to tell a live page from a hosting placeholder. |
|---|
| TCP / UDP | Whether the port is open. Databases, game servers, VoIP — anything that does not speak HTTP. |
|---|
| ICMP Ping | Packet loss and latency to the host. Useful for servers and network gear, useless for a site behind a CDN. |
|---|
| Host (SSH) | Load, disk space, memory and file descriptors on a Linux or macOS server, from one SSH login. A full disk is degraded, not an outage. |
|---|
| DNS | Whether the domain resolves and returns the records you expect. A swapped A record looks like «the site works» — just not yours. |
|---|
| TLS / SSL | Days left before expiry, chain completeness, domain match. Thresholds shrink for short-lived certificates. |
|---|
| WHOIS | Domain registration expiry. The most embarrassing outage: nobody renewed the domain. |
|---|
| WebSocket (WS/WSS) | Whether the handshake succeeds; optionally sends your message and checks the reply contains the expected text. |
|---|
| gRPC | gRPC health check, with or without TLS, against a named service. |
|---|
| SMTP / IMAP / POP3 | Whether the mail server accepts the connection and greets you over the protocol, STARTTLS included. |
|---|
| FTP / FTPS | File server availability, including explicit TLS (AUTH TLS) and self-signed certificates. |
|---|
| DNSBL | Whether your mail server's IP or domain landed on a spam blacklist — otherwise mail silently goes to junk. |
|---|
| PageSpeed | Core Web Vitals and a page performance score on a schedule, not once by hand. |
|---|
| SOCKS5 | Proxy liveness: the SOCKS5 handshake and login, and optionally a real connection through the proxy — not just an open port. |
|---|
| MTProxy | Telegram MTProto proxy availability, secret included. |
|---|
| RTSP | Whether an IP camera answers, accepts the login and has a video stream; with the video check, frames per second, bitrate and packet loss. Checked from checkers only. |
|---|
| API Check | Status code, shape and field values of the JSON response — not merely «it returned 200». |
|---|
| Transactions | A scenario in a real browser: sign in, add to cart, check out. Fails if any step breaks. |
|---|
| Heartbeat | Reverse check: your cron job pings PingZen. For backups and servers behind NAT. |
|---|
| Timings | An HTTP(S) check that times out names the step it hung at: DNS lookup, TCP connect, TLS handshake or the server's response. Checks that get a response keep their connect (DNS + TCP), TLS and TTFB times, available in the API. |
|---|