WebCheck is designed to monitor explicit pages and services that you choose. It records whether a target responded, how long it took and whether configured conditions were met; it is not a broad crawler by default.
Availability and response checks
HTTP checks request a configured URL, follow safe redirects, record the final response and compare its status with the expected range. Response duration and time to first byte are recorded for completed HTTP checks.
Content and technical checks
Content checks can compare a response baseline or look for required or forbidden text. DNS checks record A, AAAA, CNAME, MX and NS values and can detect changes. TLS checks inspect an HTTPS certificate, hostname coverage, chain, protocol details and expiry.
Other checks
TCP checks test whether a configured host and port accept a connection. Robots and sitemap checks validate the relevant public responses. Security-header checks compare configured header expectations. Domain-expiry checks can warn when a domain approaches expiry.
What WebCheck does not do
WebCheck does not silently crawl every link, submit forms, place orders or claim that an open TCP port proves an application is healthy. Choose explicit targets and treat each result as evidence about that request.