Testing Policy

TrueSignal, Inc. d/b/a SolidChecked · Effective August 17, 2026

What we check

SolidChecked runs a suite of independent checks on every product. Each check answers one question a buyer might ask. No check produces a recommendation — only observable facts.

Free checks cover everything observable from the outside: TLS configuration, DNS security, privacy policy analysis, tracker behavior, pricing transparency, contact accessibility, liveness, blocklist status, domain control, identity verification, data sharing clauses, promise-vs-behavior analysis, complaint enrollment, disclosure scanning, and secrets exposure.

Proven checks (2) require hands-on testing: email behavior monitoring (14-day agent observation after signup) and customer verification (read-only billing system connect).

How we check

Every check uses a defined, repeatable method. Methods include HTTP probing, DNS lookups, LLM-assisted document analysis, network traffic observation, and direct product testing by an automated or human agent.

The method used for each check is recorded on the product’s verification report. We never run checks that require the builder’s cooperation unless they have explicitly opted in (e.g. Stripe Connect for customer verification).

Result statuses

We use five result terms, and only these five:

  • PASS — the check ran and the product met the criteria.
  • NOTED — the check ran and produced a finding worth disclosing, but not a failure. Neutral, not negative.
  • ATTESTED — the builder provided evidence that was verified but not independently reproduced.
  • NOT CHECKED — this check has not been run yet.
  • FAIL — the check ran and the product did not meet the criteria. Failing products are never published. A FAIL result is never shown publicly.

Re-scanning

Published products are automatically re-scanned every 30 days. The re-scan runs the same checks with the same methods. If a product fails a hard-fail check during re-scan, the revocation process begins immediately.

Revocation

Certain checks are designated hard-fail: if they fail, the product’s badge is automatically revoked. When revocation occurs:

  • The badge immediately shows REVOKED across all embeds.
  • The builder is notified by email with the reason.
  • The verification report remains public as a permanent record.
  • The builder may fix the issue and re-apply. A new scan determines whether the badge is reinstated.

Independence

The fee buys the audit, never the outcome. No builder can pay for a better result. Products that fail are not published — they are unlisted and invisible to the public. We do not disclose the existence of unclaimed or unlisted products.

Complaints

Anyone can file a report about a checked product. Complaints are recorded permanently and shown as a count on the product’s verification report. We do not publish complaint text in v1 — only the count and whether the complainant verified their purchase.

History

All check results are append-only. We never delete or modify a past result. The complete dated history of every check is available on each product’s verification report.