Your First Monitor
This guide walks through creating an HTTP uptime monitor, setting alert thresholds, and connecting it to a notification channel.
Open the Monitoring page
Click Monitoring in the left sidebar.
Add a monitor
Click + Add Monitor and choose the monitor type:
| Type | Use for |
|---|---|
| HTTP / HTTPS | Websites, APIs, dashboards |
| TCP port | Databases, SMTP, custom services |
| DNS | Domain resolution correctness |
| SSL | Certificate expiry and grade |
| Keyword | Page must contain (or not contain) a string |
| Cron | Heartbeat — job must check in every N minutes |
Configure the HTTP monitor
| Field | Example | Notes |
|---|---|---|
| URL | https://myapp.com/healthz | Must be reachable from our probes |
| Interval | 5 min | 1 min available on Pro |
| Timeout | 10 s | Request timeout before declaring down |
| Expected status | 200 | Any 2xx is fine, or set a specific code |
| Keyword | {"status":"ok"} | Optional — page must contain this string |
| Locations | EU, US-East, Asia | Multi-region parallel checks |
Set alert thresholds
Scroll to Alert conditions:
Down for ≥ 2 consecutive checks → fire "Down" alert
Response time > 2000ms for 5 min → fire "Slow response" alert
SSL expiry < 14 days → fire "SSL expiry" alert
SSL grade drops below B → fire "SSL degraded" alertYou can customise every threshold.
Assign notification channels
Select which channels receive alerts for this monitor. If you haven't connected any yet, go to Notifications → Channels first.
Save and verify
Click Save. The first check runs within 30 seconds. You'll see the status badge turn green (Up) or red (Down) immediately.
Congrats — your monitor is live. SecureCheap will now alert you within seconds of a failure.
Monitor statuses
| Status | Meaning |
|---|---|
| 🟢 Up | All checks passing |
| 🔴 Down | 2+ consecutive failures |
| 🟡 Degraded | High latency or intermittent failures |
| ⚪ Paused | Manually paused |
| 🔵 Pending | Awaiting first check |