Catch the response that visitors actually receive.
What it checks
HTTP monitoring checks the configured URL against expected status codes. Error responses, missing required text and known error content can produce a failed result even when the server answers.
Set it up thoughtfully
Choose GET for content checks or HEAD for headers. Start with a public HTTPS URL, a realistic timeout and an interval your deployment can sustain. Redirect destinations need the same network protections as the first URL.
Know the boundary
A single host cannot represent every visitor location. Detection follows the scheduled interval and configured confirmation thresholds; it is not instantaneous.