Create a policy per verified asset under Monitoring → Policies → New policy. Every kind runs from our isolated monitoring network and only on verified assets.
| Kind | Runs | Watches | Alerts you get |
|---|---|---|---|
| Uptime | Every 1, 5, 15, 30 or 60 minutes (the minimum depends on your plan) | Status code, latency, keyword and TLS validity | Website down after 2 consecutive failures; website recovered |
| TLS | Every 6 hours | Certificate chain, hostname match, expiry, fingerprint, TLS 1.0 / 1.1 support, negotiated cipher | Certificate expiring at 30, 14, 7 and 1 days; invalid; changed; weak configuration |
| DNS | Hourly | A, AAAA, CNAME, MX, NS, TXT, CAA, SPF and DMARC | DNS changed (with the exact added and removed records); email authentication weakened |
| Headers | Daily | HSTS, CSP, X-Content-Type-Options, frame protection, Referrer-Policy, Permissions-Policy | Headers regressed when one goes missing or gets weaker |
| Defacement | Every 6 hours by default (1, 3, 6, 12 or 24) | Your homepage and up to 5 more pages | See Defacement and page-change monitoring |
Options
TLS port and legacy-protocol probing, DNS record types to leave out of alerts (they are still recorded, useful behind a load balancer that rotates addresses) and the page path for headers.
Alert behavior
Each problem is alerted once when it appears and marked resolved when it clears, so a certificate that stays misconfigured does not email you every six hours. Choose per trigger whether you get it in the app, by email or both under Settings → Notifications.
Where to look
Monitoring → Events (filter and acknowledge), Monitoring → Certificates (every monitored certificate, soonest expiry first) and the asset's TLS, DNS and Monitoring tabs for history. Raw uptime results are kept for 90 days and daily rollups for 2 years.