Webopsy Full report

Draft. Built from a single check on November 22, 2026. It becomes a live page, re-checked every day and after every deploy, when example.com is under Watch.

Security and privacy, independently checked

example.com

Last checked
November 22, 2026
Monitoring
Not monitored
Controls verified
3 of 9
Clean Bill of Health
Not in force

Controls

What a check of the live site, from outside, can establish. Each row is re-evaluated on every check.

Encryption in transitPartlyHTTPS, without an HSTS header.
Browser security headersNot metNot set: Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options.
No server credentials in client codeVerifiedThe page and its scripts were searched for server-side keys (payment, cloud, AI, source control); none found.
Privacy policyNot metNo readable privacy policy was found.
Policy matches what the site runsPartlyNo trackers fired to compare against, or the policy could not be read.
No tracking before consentVerifiedNo analytics or advertising trackers run on load.
Terms of serviceNot metNo terms of service found.
Vulnerability disclosure contactPartlyNo /.well-known/security.txt; researchers have no published way to report a problem.
Accessibility (automated WCAG 2.2 checks)VerifiedNo automated failures on the home page.

Sub-processors seen on the site

Third-party services a real browser saw the site load on November 22, 2026. A vendor list taken from the live site, not from a form.

None seen.

Security questionnaire answers

The questions vendor reviews ask that outside evidence can answer. Copy them into a questionnaire, or send this page.

Is data encrypted in transit?
Partly. HTTPS, without an HSTS header.
Do you use security headers such as Content-Security-Policy and HSTS?
No. Not set: Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options.
Are secrets and API keys kept out of client-side code?
Yes. The page and its scripts were searched for server-side keys (payment, cloud, AI, source control); none found.
Do you have a published privacy policy?
No. No readable privacy policy was found.
Which third parties (sub-processors) receive data from your website?
None were seen loading on the live site.
Do you obtain consent before setting non-essential cookies?
Yes. No analytics or advertising trackers run on load.
Do you have a process for receiving vulnerability reports?
Partly. No /.well-known/security.txt; researchers have no published way to report a problem.
Do you monitor your public-facing systems for security and privacy regressions?
Not continuously. This page reflects a single independent check.

Record of checks

Every independent check of example.com, newest first. Nothing is removed from this list.

CheckedScoreOpen findingsTrackers before consent
Nov 22, 2026, 11:48 a.m.536None
Nov 22, 2026, 11:17 a.m.536None
Nov 22, 2026, 10:13 a.m.536None
Nov 22, 2026, 9:26 a.m.536None
Nov 22, 2026, 8:36 a.m.536None
Nov 22, 2026, 7:56 a.m.536None
Nov 22, 2026, 7:02 a.m.536None
Nov 22, 2026, 5:50 a.m.536None
Nov 22, 2026, 5:10 a.m.536None
Nov 22, 2026, 4:23 a.m.536None
Nov 21, 2026, 4:19 p.m.536None
Nov 21, 2026, 3:20 p.m.536None
Nov 21, 2026, 2:29 p.m.536None
Nov 21, 2026, 1:30 p.m.536None
Nov 21, 2026, 12:06 p.m.595None
Nov 21, 2026, 8:11 a.m.536None
Nov 21, 2026, 12:14 a.m.536None
Nov 20, 2026, 10:51 p.m.536None
Nov 20, 2026, 10:08 p.m.536None
Nov 20, 2026, 9:18 p.m.536None
Nov 20, 2026, 8:29 p.m.536None
Nov 20, 2026, 5:48 p.m.536None
Nov 20, 2026, 4:25 p.m.536None
Nov 20, 2026, 3:19 p.m.536None
Nov 20, 2026, 2:33 p.m.536None
Nov 20, 2026, 1:19 p.m.536None
Nov 20, 2026, 12:41 p.m.536None
Nov 20, 2026, 11:56 a.m.536None
Nov 20, 2026, 11:16 a.m.536None
Nov 20, 2026, 10:46 a.m.536None

What this page does not cover.

It is an independent check of the public site, not an audit and not SOC 2. These cannot be seen from outside, so they are not answered here; ask example.com directly:

Checks are run by Webopsy, which example.com does not control. What each check verifies. Machine-readable: JSON.