Web & Domains
HTTP/HTTPS Monitoring
HTTP monitoring sends a real request to your endpoint on every interval and validates status code, response time, TLS validity and optional keyword content — so a 200 that says 'maintenance mode' still counts as down.
The check every outage story starts with
What it checks
- HTTP status codes and expected response patterns
- End-to-end response time including TLS handshake
- Keyword presence or absence in the response body
- Certificate expiry on HTTPS endpoints
- Redirects, custom headers and request methods
Set it up
- 1Create an HTTP monitor with your endpoint URL
- 2Set expected status codes and an optional keyword assertion
- 3Pick your interval — down to 15 seconds on higher tiers
- 4Attach contacts and an escalation policy
FAQ
Can HTTP monitoring check behind authentication?
Yes — monitors support custom headers and methods, so bearer tokens or API keys can authenticate the probe request.
How fast are HTTP checks?
Intervals go down to 15 seconds. Each check is a lightweight request — thousands of daily checks against a production endpoint are negligible load.
Related check types
Start monitoring in minutes
External probes plus internal agents, escalation chains and status pages — free tier, no card required.