HTTP / HTTPS monitoring

Monitoring that tells you why.

Most monitors tell you a page is slow and stop there. CuliPulse breaks every request into its real stages — DNS, connect, TLS, server wait, download — and tells you, in plain words, where the time actually went.

Start free See what you can check
No credit card · free plan forever
api.acme.com · 200 · 624ms
DNS
49ms
Connect
38ms
TLS
75ms
Wait
450ms
Download
12ms
Your server is the bottleneck — 450ms spent waiting for the first byte, not the network.
Find out why, on demand

Stop guessing where the time goes.

Every check records the full timing breakdown, so a slow page isn't a mystery — it's a labelled chart with a verdict. Need a fresh read right now? Hit Diagnose now and an agent runs a cold, one-shot probe and reports the phase-by-phase timing in seconds.

Phase breakdown on every check

DNS, connect, TLS handshake, server wait and download — captured automatically and turned into a plain-language verdict, not raw numbers you have to decode.

Diagnose now

An on-demand, fresh-connection probe for the moment you need an answer. Cold timings, no caching, results in seconds.

▸ Diagnose nowcold connectionTLS 75ms · wait 450ms
Beyond "is it up?"

Check what the response actually says.

Status codes

Match an exact code, a whole class, or a list — and decide which ones count as healthy.

2002xx200,302

Response body

Assert the body contains (or doesn't contain) text, or matches a regular expression.

contains "Welcome"~ /order-\d+/

JSON responses

Pull a value out by path and check it equals, contains, exists, or is greater / less than expected.

$.status == ok$.items > 0

Response headers

Assert a header equals, contains, matches a pattern, or simply exists.

content-type ~ jsonx-cache exists

Authentication

Send a Bearer token or Basic credentials with every check — stored encrypted, never shown back.

Bearer ••••••Basic ••••••

Response time

Flag “up but slow” before your users feel it, as a distinct degraded state.

< 800ms → degraded

Plus custom methods, request headers and bodies, a follow-redirects toggle, and a default User-Agent you can override.

Fewer false alarms

Confirmed from several places before you're paged.

Add more than one checkpoint and CuliPulse waits for several of them to agree before it calls something down. One bad network hop won't wake you up — and when we do alert, it's real.

checkout.acme.com · 2 of 3 agree
apac timeout
weur 502
enam 200
2 of 3 regions agree it's down → alert sent. A single flaky region never pages you.
CuliPulse
🔴 checkout.acme.com is down
Confirmed from 2 places · 1m ago
HTTP 502 from origin
SSL / TLS

Never get surprised by an expired certificate.

Turn on certificate monitoring and we warn you a set number of days before it expires — with the exact days-left and expiry date right on the monitor. One checkbox, no maths. It rides on the same monitor as your status, body and header checks, so one endpoint means one monitor and one alert.

shop.acme.com
certificate expires in 12 dayswarn at 14
Apr 30, 2026 · checked from agent “prod-1”

Watch your first endpoint in 2 minutes.

Add an HTTP monitor, see the phase breakdown, and get alerts you can trust. Every feature is on the free plan.

Start free