Free tool, no signup
Health check endpoint tester
Enter your /healthz, /health or /status URL. We call it once right now and grade the four things that decide whether a load balancer or monitor can trust it: status code, response time, body, and cache headers.
How it grades
- Status code. 2xx passes. A redirect warns, because checks should hit the final URL. Anything else fails, including 401 and 403: a health check that needs a password is one most load balancers cannot call.
- Response time. Under 300ms passes, under 1000ms warns, slower fails. A health check answers from memory or one cheap ping, not a full dependency sweep.
- Body. Empty, short text, or small JSON passes. An HTML page fails (that is usually a catch-all route), and so does anything that looks like a stack trace, a connection string or a credential field.
- Caching.
Cache-Control: no-storepasses. A missing header warns. A cacheable header, or a response that came from a cache, fails: a cached 200 can stay green while the origin is down.
We read at most the first 16 KB of the body, scrub anything secret-shaped before grading, and keep nothing. The request goes through the same guarded path our monitoring uses, so private and internal addresses are refused.
A health endpoint nobody calls is decoration
This test is one request from one place. RealUptime Monitor calls your health endpoint on a schedule from four regions (US-East, US-West, Europe, and Asia-Pacific) on Free, can assert on its status and body, and alerts you when it fails. For what a good health endpoint returns, read the health check endpoint guide.
More free tools
Is my website down?: check whether a site is reachable right now. SSL certificate checker: expiry, lifetime and issuer. See all free tools.