Healthchecks
Healthchecks continuously verify that your targets' services are up and responding correctly. When a service goes down, alerts are triggered within 15 seconds through your configured alert channels.
Endpoints
Healthcheck endpoints are linked to your existing targets, allowing you to monitor service availability alongside your security scans. This unified view helps you track both security posture and service health in one place.
Monitor
A monitor is a probe used against an endpoint. You can configure multiple probes (HTTP, HTTPS, TCP, ICMP) against a single target.
Monitor types
| Type | Use case | Configuration |
|---|---|---|
| ICMP (ping) | Basic network reachability | Timeout only |
| TCP | Verify port connectivity for databases, SSH, or custom services | Port number, timeout |
| HTTP | Monitor web services, APIs, and web applications | Method (GET/POST), expected status code, timeout |
| HTTPS | Monitor secure web services with SSL/TLS encryption | Method (GET/POST), expected status code, timeout, certificate validation |
Monitor status
Healthchecks report one of three states:
- Healthy → Service is healthy and responding as expected
- Unhealthy → Service is unreachable or not responding correctly
- Unknown → Monitor is initializing or status cannot be determined. Contact support at [email protected] if this persists.
Egress IP reference
Healthchecks are performed from our monitoring infrastructure. Use this IP to identify our health check requests and allow them in your firewalls:
| IPv4 Egress | IPv6 Egress |
|---|---|
51.91.190.7 | 2001:41d0:303:5d42::10 |
Alerting
When a health check changes status (e.g., from Healthy to Unhealthy), alerts are automatically triggered through your configured alert channels to notify you immediately of service outages.