HTTP monitoring
Why redirects can cause a monitoring failure
Understand redirect chains, broken destinations, HTTPS downgrade protection and hostname changes in WebCheck.
Read article →WebCheck help centre
Practical guides for understanding checks, diagnosing warnings, confirming incidents and sharing service status with your customers.
HTTP monitoring
Understand redirect chains, broken destinations, HTTPS downgrade protection and hostname changes in WebCheck.
Read article →Monitoring basics
Understand how WebCheck identifies slower responses, why degraded is not automatically downtime and what to investigate next.
Read article →Monitoring basics
Run an immediate WebCheck check, understand the queue message and avoid confusing a manual result with a scheduled run.
Read article →Monitoring basics
Monitor a public TCP service by host and port, understand connection failures and know what an open port does not prove.
Read article →Notifications
Configure a WebCheck webhook, understand its JSON payload and verify optional HMAC signing safely.
Read article →Product guidance
Understand the current WebCheck site, target, interval, history and notification limits and why they affect monitoring setup.
Read article →DNS monitoring
Understand resolver caching, address-family differences and how to compare WebCheck DNS evidence with a local lookup.
Read article →Notifications
See what WebCheck retries after an alert delivery fails and what to check when a notification does not arrive.
Read article →Notifications
Learn how incident confirmation, the site notification delay and background delivery affect alert timing.
Read article →Incidents
Use the incident diagnosis, timeline and related check runs to find the cause and confirm recovery.
Read article →Product guidance
Compare the questions simple availability checks and WebCheck’s additional monitoring signals can answer.
Read article →