Uptime · Module 5/5

4 monitor kinds,
smart alerting + AI post-mortem.

Snapshot scans aren't enough. HTTP/HTTPS + DNS + TCP + Playwright synthetic (behind-login flows), checked from our monitoring node in the Netherlands. A 3-fail / 2-ok rule keeps one blip from paging anyone. 6 alert channels. When the incident closes, an AI model drafts the post-mortem from the timeline. Public status page + embed SVG badge.

Set up monitor Explore the features
4
Monitor kinds (HTTP/DNS/TCP/Synthetic)
6
Alert channels (Slack/Discord/Teams/Telegram/Email/Webhook)
5
On-call escalation tiers
14
Uptime + security plugins
14 plugins + 4 monitor types

Uptime capability map

MonitorHTTP/HTTPS Monitor (keyword + redirect chain)
MonitorDNS Monitor (A/AAAA/MX/TXT/CAA/NS/CNAME × dnspython)
MonitorTCP Monitor (port-open probe)
MonitorSynthetic (Playwright: login + checkout flow)
HeadersSecurity Headers (Mozilla Observatory A+)
HeadersCookie Prefix Integrity (__Host- / __Secure- attribute validation)
CORSCORS Misconfiguration (reflected-origin + null-origin probes)
TLSTLS Deep (TLS 1.3 + modern cipher + chain)
TLSHSTS Preload Eligibility (max-age + includeSubDomains + preload)
CertsCertificate Transparency (crt.sh subdomain inventory, issuing CAs, wildcards)
DNSDNS Health (DNSSEC/SPF/DKIM/DMARC/CAA)
DNSSubdomain Takeover (dangling CNAMEs at unclaimed cloud services)
RedirectRedirect Chain (hop count, HTTPS→HTTP downgrade, loops)
RedirectOpen Redirect (unvalidated off-site redirect parameters)
MailMTA-STS & TLS-RPT (RFC 8461 policy + RFC 8460 reporting)
MailBIMI Brand Indicator (default._bimi record + VMC/CMC verified mark)
FilesExposed Files (.git, .env, SQL dumps, swagger, phpinfo)
DiscoveryWell-Known Resources (security.txt, GPC, app links, OIDC)
Incident workflow

From open to close

Smart alerting

Fewer false alarms, every channel

An incident opens only after three failed checks in a row and closes after two good ones. On open, 6 channels fire in parallel; up to 5 on-call escalation tiers; on close, an AI model drafts a short post-mortem from the timeline, labelled as an AI draft.

  • HTTP/DNS/TCP/Synthetic dispatch — worker per kind
  • 3-fail / 2-ok state machine
  • Per-tier delay_minutes, acknowledge stops the chain
  • Incident timeline (append-only event log)
incident: monitor #142 — recovered
• 14:32:08 — check failed (timeout 30s)
• 14:32:38 — check failed (5xx)
• 14:33:08 — check failed (5xx) — incident OPENED (3 in a row)
• 14:33:09 — alert dispatched: slack, telegram
• 14:38:42 — incident CLOSED after 2 good checks (Δ 5m 34s)
✨ AI-drafted post-mortem attached
Status page + embed badge

Visible reliability for your customers

Public status page (slug globally UNIQUE) + Shields.io-style embed SVG badge + 30-day uptime %. White-label v1.0: subpath + accent_color + logo_url.

Uptime uptime + synthetic in 5 minutes.

One monitor on Free; 5 on Freelancer, 15 on Studio, 50 on Agency.

Set up monitor See all 5 modules