Skip to content
RequestGuard Website Monitoring
Pricing

Website monitoring methodology

What our website
checks establish.

A public profile describes observations of one exact hostname. It is a dated record of defined checks, not a business certification or a guarantee against compromise.

Required baseline

ConnectionHTTPS and TLSAccessible HTTPS without a blocking challenge, a valid hostname certificate, TLS 1.2 or newer, and HTTP-to-HTTPS redirection.
Browser protectionsResponse headersHSTS, framing protection, and content-type protection through nosniff.
Threat reputationConfigured sourcesCurrent, conclusive evidence from the configured malware, threat-DNS, and blocklist checks.
Public exposureSelected pathsCompleted, conclusive checks of the selected path catalog, with no confirmed exposure or finding requiring review.

CSP quality, referrer and permissions policies, CAA, and DNSSEC are recommendations. Search visibility and network location do not determine whether the baseline passed.

Coverage and freshness

Missing required evidence means Incomplete. A required failure or exposure needing review means Needs attention, even if other checks could not finish. Passed requires all baseline requirements to be satisfied. Evidence older than 48 hours is Stale.

Checks run daily while monitoring is enabled and domain control remains verified. A service being active does not mean its checks passed. Payment and manual acknowledgments never improve the published result.

Limits and private findings

Checks are bounded and unauthenticated. They do not establish the security of every page, account, plugin, application function, or business process. Sensitive exposure paths and evidence require verified access. Public profiles show a scoped summary approved for publication by the workspace owner.