DeadWatch reads the full health picture of every site you manage — not just whether it responds, but how fast, how it looks, what it exposes, and when its certificate lapses. Each monitor is optional per site and runs on the site's own interval. Here's what the watch actually covers.
Every check records a response time, an HTTP code and a classified reason code — curl_timeout, http_503, success_slow — so the why is legible. A single failure never pages you: DeadWatch re-checks from a second region before opening an incident.
DeadWatch screenshots each monitored URL and compares it against an approved baseline, reporting diff_percent per breakpoint. A change that only breaks on mobile is still caught, and an anomalous jump stands out against the page's own rolling history.
Measured in a real headless browser: LCP, FCP, CLS, TBT, TTFB and INP, plus TTI, Speed Index and page weight. DeadWatch computes a 0–100 score with Lighthouse-style log-normal scoring, weighted toward the metrics users feel most, and maps it to an A–F grade.
A certificate about to lapse, an MX record that vanished, a domain nobody renewed — none of these throw an error page. They just take the site down when nobody's looking. DeadWatch tracks all three and warns you with real lead time.
DeadWatch reads the hardening posture expressed in each site's response headers and folds a security_score into the health picture as the Security pillar. It's the monitoring-side security signal — whether the right protections are actually set.
Events flow event → router → channel. Routing rules match on event types like uptime.down or uptime.recovered and dispatch to the channels you've wired for that rule. Delivery is durable — queued through an outbox and logged — so a briefly-unreachable channel never loses an alert.
Sites belong to teams; access is role-based, and a client can be given scoped access to their own sites — their uptime and health, without your roster or your other clients.
super_admin, admin, member, viewer and api_token, with granular capability strings — sites:*, incidents:*, notifications:* — so access is shaped precisely.
Give a client access to only their sites. They see their status; your roster and other clients stay private. Route their alerts to their own Slack.
Each agency runs on its own instance at its own subdomain — your data in your own database, never mixed with another agency's.
Beyond the headline monitors, DeadWatch tracks the integrity, network and search signals that quietly decide whether a site stays healthy. All shipped, all optional per site.
A, AAAA, MX, TXT, NS, CNAME and SOA records tracked, with an audit that flags a moved nameserver or a vanished mail record — often the first sign of trouble.
Registrar, expiry date and status via WHOIS/RDAP, with weeks of lead time before a domain nobody renewed silently drops the site.
TCP port reachability and ICMP-style ping checks for latency and liveness, so a service that stops listening is caught at the network layer.
Hash-based change tracking with a stability score — know when a page's content shifted, intentionally or not, without watching it by hand.
Crawls the links on a site and tracks broken, redirected and healthy targets over time, so dead links surface before a visitor hits one.
Fingerprints JS and CSS assets and flags new, removed or changed files — a fast read on what a deploy actually shipped, or what a third party slipped in.
Robots.txt, sitemap and canonical tracking, plus keyword-rank position monitoring — the ranking signals that erode without ever throwing an error.
Detection for redirect hijacking, cloaking, spam injection and hidden links — a compromise caught before it wrecks reputation or search standing.
Scheduled-job liveness so a silently-dead cron gets noticed, and apex-vs-www parity so the two versions of a site don't drift apart.
Pick a plan and check out through Stripe; manage your subscription, add stackable packs, and see invoices from your account portal. No sales call required to start.
Give clients scoped access to their own sites, and shape exactly what each role sees with the View-Group visibility matrix. A built-in knowledgebase covers the rest.
Support tickets when you need a hand, and a dedicated instance per tenant at your own subdomain — hosted by us, or self-hosted if that's a hard requirement.
Get set up in minutes. See how the workflow fits together, or read the monitoring reference for the full detail.