Website & API monitoring
Point PingDog at a URL and it makes a real HTTP request on your schedule — validating the status code, measuring the round-trip, and optionally matching a string in the response body — then alerts you the moment the check fails.
What PingDog checks
- HTTP / HTTPS status code (default: expect 200; set any code you require)
- End-to-end response time (DNS + TCP + TLS + HTTP round-trip)
- Optional response-body substring match — catch a page that returns 200 but renders an error
- GET or POST, with a configurable timeout
An HTTP check is the workhorse of uptime monitoring. A homepage that "loads" can still be broken — a 200 response wrapping a stack trace, a health endpoint that stopped returning "ok":true, a login page timing out under load. Matching the body and the status code together catches the failures a bare ping misses.
Because PingDog is anonymous and pay-per-check, you can watch a single critical endpoint at a fast interval for a short burst — a deploy window, a sale, an incident — without a monthly plan, and stop the moment you're done.
Anonymous, pay-per-check
Like everything on PingDog, this check needs no account: your key is the account, you pay once at $0.0005 per delivered check in USDC on Base, and nothing renews. A real free tier runs up to 3 monitors at a 5 minutes interval with no payment at all. See how pricing works.
Frequently asked
Can PingDog check for a specific word in the response?
Yes. Set an expected body substring and the check fails if the response does not contain it — so a page that returns HTTP 200 while actually rendering an error is still caught as down.
Can I monitor an API that needs a POST?
Yes. HTTP checks support GET or POST with a configurable timeout and expected status code, so you can probe a health endpoint that expects a POST.