Websites

Visual guide to website and service checks

Review HTTP, TLS and linked service evidence without confusing one success with full coverage.

Separate the checks

A registered website may have HTTP response history and HTTPS certificate evidence. A linked service belongs to its server and has its own check scope. The diagram groups those concepts; it does not depict a live customer asset.

Illustrative flow connecting a registered website to HTTP, TLS and related service evidenceIllustration only. No domain, service status or certificate date is fabricated.

Review sequence

  1. Confirm the website and workspace selected in the Monitor.
  2. Read the original HTTP target, redirects, final response and check time.
  3. For HTTPS, inspect certificate hostname, validity and expiry separately.
  4. If the service depends on a registered server, check agent freshness and its service template.
  5. Compare with history and alert delivery before reporting an incident resolved.

Coverage warning

HTTP availability, TLS validity and service health are different observations. None proves that an application is free of vulnerabilities. See website status and SSL, service health, and security coverage.

Before taking action

Confirm the active workspace, required permission, registered asset, and freshness of the data being used.

← Back to documentation