HTTP/HTTPS Monitoring
Monitor websites, APIs, and web services with comprehensive HTTP/HTTPS checks including custom requests, response validation, and SSL certificate monitoring.
Basic Configuration
URL
The full URL to monitor, including protocol (http:// or https://).
https://example.com
https://api.example.com/health
http://internal-service:8080/status
Check Frequency
How often to check your endpoint. Options range from 10 seconds to 60 minutes. More frequent checks provide faster issue detection but consume more resources.
Timeout
Maximum time to wait for a response before considering the check failed. Default is 10 seconds. Adjust based on your endpoint's expected response time.
Request Configuration
Note: Response bodies are limited to 8KB to prevent excessive data transfer. Only the first 8KB of the response will be downloaded for validation checks.
HTTP Methods
Choose the appropriate HTTP method for your endpoint. Default is HEAD for efficiency.
Retrieve full response
Submit data
Headers only (default)
Update resource
Remove resource
Partial update
Check allowed methods
Custom Headers
Add custom HTTP headers to your requests. Useful for authentication, API keys, or custom requirements.
Enter each header on a new line in the format: Header-Name: value
Request Body
For POST, PUT, and PATCH requests, you can include a request body.
Important: Remember to set the appropriate Content-Type header (e.g., application/json) when sending a request body.
Response Validation
Expected Status Codes
Define which HTTP status codes indicate a successful response. By default, any 2xx status code (200-299) is considered successful.
200 (single status)
200,201,204 (multiple statuses)
200-299 (range)
200-299,301,302 (combination)
Leave empty to accept all 2xx status codes (200-299) as successful.
Expected Response Headers
Verify that specific headers are present in the response. The check fails if any expected header is missing or has the wrong value.
X-API-Version: 2.0
Content-Type: *
Use * as the value to check that a header exists without validating its content.
Expected Response Body
Check if the response body contains specific text. Useful for verifying API responses or ensuring pages load correctly.
"status":"ok"
<h1>Welcome</h1>
"healthy":true
The check passes if the response body contains this exact substring (case-sensitive). Only the first 8KB of the response body is checked.
SSL Certificate Monitoring
Check Certificate Expiration
Enable this option to monitor SSL certificate expiration for HTTPS URLs. You'll receive warnings at:
- ⚠️30 days before expiration
- ⚠️14 days before expiration
- ⚠️7 days before expiration
- 🚨1 day before expiration
Note: Certificate checks are performed at least once daily, independent of your monitor's check frequency. This is included with HTTP/HTTPS monitoring at no extra cost.
Additional Options
Follow Redirects
Enable to automatically follow HTTP redirects (3xx status codes). When enabled:
- • The monitor follows up to 5 redirects
- • Final destination status determines success
- • Response time includes all redirect hops
- • Useful for shortened URLs or load balancers
Disable this if you need to monitor the redirect response itself (e.g., to verify a redirect is working correctly).
Common Use Cases
Website Monitoring
Monitor your website's home page with GET request, follow redirects enabled, and response body validation for key content.
API Health Checks
Use GET or POST to health endpoints, validate JSON responses, check specific status codes, and include authentication headers.
GraphQL Endpoints
POST requests with GraphQL queries in the body, Content-Type header, and response validation for expected data structure.
Protected Endpoints
Monitor APIs that require authentication by including Bearer tokens, API keys, or other auth headers in your requests.