Supported Protocols

Every protocol OpsKitty supports and what each one checks.

HTTP / HTTPS

The most common endpoint type. OpsKitty sends an HTTP request (GET, POST, PUT, DELETE, PATCH, HEAD, or OPTIONS) and evaluates the response status code, response time, and optionally the response body. Supports custom headers and a request body. HTTPS endpoints also report TLS certificate expiry.

TCP

Verifies that a TCP port is open and accepting connections on a given host and port. Useful for monitoring databases, mail servers, game servers, or any service that does not use HTTP. The check passes when a connection is successfully established within the timeout.

DNS

Queries a DNS nameserver for a specific record and optionally validates the response. Supports A, AAAA, CNAME, MX, TXT, NS, and SOA record types. Use this to alert when DNS propagation fails or an authoritative record changes unexpectedly.

ICMP (Ping)

Sends ICMP echo requests to a host and measures round-trip time and packet loss. Useful for checking raw network reachability of servers, routers, or IoT devices. The check passes when the host responds within the configured timeout.

SSH

Attempts to authenticate via SSH using a username and password or private key. Optionally runs a shell command and checks that the output contains an expected string. Use this to verify that a server is not only reachable but able to execute commands — useful for checking the health of background workers or database connections from the server itself.