WebCheck monitors the targets you add. It checks public HTTP pages and TCP ports, and can inspect DNS, TLS, security headers and domain expiry. It does not crawl a site or run browser journeys.
HTTP pages and text checks
An HTTP check sends a GET request, follows safe redirects and compares the final status with the range on the target. It records response timing and a content hash. In the current dashboard, you can also require or forbid an exact phrase in the server response; there is no setting for approving a full-page content baseline.
DNS, TLS and other checks
The homepage checks created during setup include DNS and, for an HTTPS homepage, a separate TLS check. DNS records cover A, AAAA, CNAME, MX and NS. TLS checks validate the certificate and report certificate and protocol details. You can add TCP port, security-header and domain-expiry checks where the target form offers them.
Checks WebCheck does not offer
The current dashboard has no dedicated robots.txt or sitemap validator, and it does not parse canonical or noindex tags. You can monitor those URLs as ordinary HTTP targets, but WebCheck will not validate their document structure or SEO directives.
Keep the result in perspective
WebCheck does not crawl every link, submit forms, place orders or test a page in a logged-in browser. A successful TCP connection confirms that a port accepted a connection; it does not prove that the application behind it is working.