Documentation
Check types
- HTTP / HTTPS — Monitor status code and response time
- SSL Certificate — Verify certificate trust, hostname and expiry
- DNS — Verify DNS records resolve as expected
- TCP Port — Check host:port connectivity
- SMTP — Verify email servers on ports 25 and 587
- Ping — ICMP host reachability
- API — HTTP with custom headers, body, and response assertions
- Domain Expiry — Track domain registration expiry via WHOIS
- Blacklist — DNSBL spam-blocklist listing check
- Security Headers — Verify required security response headers
- Core Web Vitals — Lighthouse performance score and LCP via PageSpeed
- Synthetic Transaction — Multi-step scripted test scenario
- Link Checker — Crawl site and find broken links
- Heartbeat — Cron / backup job monitoring via ping
Notifications
Each check can notify by email, Slack (incoming webhook URL), or SMS (Vonage). Alerts fire on a state change — when a check goes down, recovers, or a certificate enters its expiry-warning window. A check must fail twice in a row before paging, and URL checks are verified from a second location first, so a blip at one vantage point never wakes you up.
Incidents & status pages
Every confirmed outage opens an incident that tracks its duration, cause, and an
AI-written post-mortem after recovery. Publish selected checks on a public status
page (/s/your-slug) with 90-day uptime history, email subscribers,
maintenance notices, and embeddable SVG uptime badges.
REST API & webhooks
The full API is available on every plan: manage monitors, read incidents, and
subscribe webhooks that fire when a monitor goes down or recovers (the backend for
our Zapier triggers). Authenticate with an X-Api-Key
header — issue
keys on the in-app API page, and see the OpenAPI spec
for every endpoint.