Short guides to each part of CuliPulse — what it checks, how to set it up, and why it works the way it does. We're publishing one per feature; more on the way.
Status, body / JSON / header checks, a latency phase-breakdown that tells you why a page is slow, multi-region confirmation, on-demand diagnosis, and TLS-certificate expiry.
Read the guide →
Get warned before a domain's registration lapses — agentless, daily, with days-remaining + registrar. As a standalone monitor or an add-on to any site.
Read the guide →
Watch A, AAAA, CNAME, MX, TXT and NS records against an expected baseline — catches hijacks, deploy drift, and MX misconfig fast. Agentless, edge-resolved via DNS-over-HTTPS.
Read the guide →
Databases, brokers, and anything that listens — checked from CuliPulse or from inside your network.
Read the guide →
Plain reachability for hosts and devices, from an agent on your network.
Read the guide →
Send a payload and check the reply — DNS, game servers, and other connectionless services.
Read the guide →
Cron jobs, workers and scheduled tasks check in with a ping each run — if one goes quiet past its deadline, you're alerted. Report failed runs, time how long runs take, no agent needed.
Read the guide →
Run a small helper inside your network to watch private and internal services the public internet can't reach — and to discover them in the first place.
Read the guide →
Have an agent scan a network range (a CIDR) for open services, or point it at your AWS account — CuliPulse finds servers, databases, load balancers and open ports, and you adopt them as monitors in a click.
Read the guide →
Add your first monitor in a couple of minutes. Every feature is on the free plan.
Start free