Every setting explained — from the URL and expected status code to SSL checks, alert sensitivity and webhooks.
Each website you monitor is a "site" (or monitor). Most sites need nothing more than a URL, but a handful of optional settings let you tune exactly what counts as healthy and how sensitive the alerts are.
| Setting | What it means |
|---|---|
| Check interval | How often uptime checks run. Set by your plan — shown for reference, not editable per site. |
| Timeout | How long to wait for a response before treating the check as failed (default 10s, 1–30s). |
| Expected status | The HTTP code that counts as healthy (default 200). Change it if your site legitimately returns something else. |
| Follow redirects | Whether to follow redirects to the final page before judging the result. |
| Verify SSL | Whether to fail the check on an invalid HTTPS certificate. |
| SSL check + threshold | Enable certificate monitoring and choose how many days before expiry to warn you (default 30). |
| Homepage audit | Enable the daily homepage health check (blank page, backend error, noindex, SEO basics). |
| Alert sensitivity | Strict / Standard / Quiet — Quiet doubles the cooldown between repeat alerts so you hear less. |
| Alert email | Send this site's alerts to a specific address instead of your account default (handy per-client). |
| Webhook URL | POST alert events to your own endpoint (Slack, automation, etc.) in addition to email. |
These tools are one-off checks. A Monitrova account monitors your sites continuously and emails you the moment something breaks.