An HTTP check sends a bounded GET request to the target URL and compares the response with that target’s settings. WebCheck records the final URL, status, response time, time to first byte, redirect chain and a content hash; it does not keep a copy of the response body.
Expected status range
The default range is 200–399. Edit the target if your endpoint has a different response contract; accepting a status code only confirms that response, not that a user journey worked.
Redirects and safety
WebCheck follows redirects one hop at a time, validates each destination and stops after five hops. It blocks restricted destinations and will not follow an HTTPS URL down to HTTP.
Timing and request limits
Each request has connection and total timeouts and a default 2 MB response-body limit. WebCheck records the total duration and time to first byte. A response can be marked Degraded when it is substantially slower than that check’s recent successful runs.
What a successful GET tells you
It shows that this public request reached the endpoint and met the configured response conditions. It does not sign in, submit a form, complete a checkout or prove that every visitor can reach the site.