HTTP monitoring

Watch every site and API you run.

Point Hesklo at a URL and it requests it on your interval. Match an exact status code or accept any 2xx, and optionally require a string in the response body so a page that loads but returns nothing still counts as down.

Status code or body match. Require an exact code, any 2xx, or a string that has to appear in the response.
SSL expiry tracked free. Every HTTPS check counts down the certificate and warns you well before it lapses.
Your own interval and timeout. Each monitor runs on its own schedule, from tight checks on an API to a slower loop on a marketing site.

Start free All features

01 · What it checks

More than "did the page load".

A server can answer with a 200 and still be broken. HTTP monitoring lets you say what a healthy response actually looks like.

Exact status code

Require a specific code. Useful when an endpoint is meant to return a 201 or a 301 and anything else means something changed.

Any 2xx

The forgiving option. Anything in the success range passes, so a redirect chain or a varying code does not page you.

Body content match

Require a string to appear in the response. Catches the case where the app serves a shell page with an empty or errored payload.

Response time

Every check records how long the request took, so you can see a service degrading before it fails outright.

SSL certificate expiry

Any HTTPS monitor tracks days remaining on the certificate. Branch on it in a policy and get warned ahead of time.

Custom timeout

Set how long to wait before a request counts as failed, so a slow endpoint is judged on its own terms.

02 · Before it pages

A blip is not an outage.

Confirm after several fails

Require a number of consecutive failed checks before the monitor is marked down. One dropped request never wakes anyone.

Run a check now

Probe the URL on demand and see the exact response, without waiting for the next scheduled run.

Maintenance windows

Pause the monitor during planned work. It keeps its history and resumes exactly as it was.

Flap dampening

A cooldown on each notify step, so a service bouncing up and down does not turn into a hundred messages.

Questions

Common questions

Can Hesklo check that a page contains specific text?

Yes. On any HTTP monitor you can require a string to appear in the response body. If the request succeeds but that string is missing, the check fails. This catches the common case where an application returns a 200 while the underlying data or service behind it is broken.

Does Hesklo monitor SSL certificate expiry?

Every HTTPS monitor tracks the certificate expiry date automatically. There is nothing extra to configure. You can also branch on it inside an escalation policy, for example alerting a channel when a certificate has fewer than fourteen days remaining.

How often can an HTTP check run?

Each monitor has its own interval and its own timeout, so you can check a critical API frequently and a low-traffic marketing site far less often. The available intervals depend on your plan.

Will a single failed request wake someone up?

Not unless you want it to. A monitor can require several consecutive failed checks before it counts as down, and each notify step has its own cooldown. Between those two controls a brief blip stays quiet.