Monitoring

How often are certificates checked?

You set a scan frequency per monitor, up to 86400 seconds (24 hours). The minimum depends on your plan: 30 minutes on Business and Enterprise, 1 hour on Pro, 6 hours on Startup. Requests below your plan’s floor are rejected with INTERVAL_TOO_SHORT; if you omit the field when creating a monitor, it defaults to your plan’s minimum.

How often are uptime checks run?

You set a check interval per monitor, up to 3600 seconds (1 hour). The minimum depends on your plan: 30 seconds on Business and Enterprise, 60 seconds on Pro, 300 seconds on Startup.

What does a certificate check look at?

Each scan records the certificate’s expiration date, issuer, and the negotiated TLS version and cipher suite. CertWatch.io also probes the minimum TLS version and cipher the server still accepts. A server that negotiates TLS 1.3 with modern clients but still accepts TLS 1.0 gets flagged as weak.

Can I monitor non-standard ports?

Yes. Both monitor types support custom ports. Uptime monitors additionally support HTTP or HTTPS protocol selection, custom request paths, expected status codes, timeouts, and response string matching (assert that a string is present or absent in the response body).

What counts as “down” for an uptime monitor?

A check fails when the endpoint does not respond in time, returns an unexpected status code, or fails the configured string match. Alert rules control how failures turn into alerts, so a single blip does not have to page you.

Can I pause a monitor without deleting it?

Yes. Disabling a monitor stops its checks and keeps its configuration and history. Re-enable it any time. Disabled monitors still count toward your plan’s monitor limit; deleting a monitor frees the slot.

How do I get my check history?

Certificate and uptime check history is available in the dashboard and via the API (per-monitor detail endpoints and the analytics endpoints for aggregated trends). Export endpoints return monitor lists as CSV or JSON.