Use HTTPS when the production service is intended to be secure. WebCheck treats the scheme as part of the target: HTTPS requests receive strict TLS validation, while HTTP targets do not receive a TLS check.
What changes between HTTP and HTTPS
An HTTP target uses the public HTTP request path and can receive the initial HTTP and DNS checks. An HTTPS target also receives a TLS check, which inspects certificate and protocol health.
Redirects are part of the result
If HTTP redirects to HTTPS, WebCheck records the redirect chain and evaluates the final response. A redirect to an invalid, restricted or unexpected destination can still make the check fail.
HTTPS is not downgraded
WebCheck does not follow an HTTPS target down to HTTP. This prevents a secure monitoring target from silently becoming an insecure request. Certificate hostname, chain and protocol validation remain enabled.
What this proves
A successful HTTPS check shows that this monitoring request reached the configured public endpoint and passed its response conditions and TLS checks. It does not prove that every page, browser journey or user network is healthy.