Changelog

What changed

A short record of meaningful changes to the public ThreatScope Check experience. Technical contract versions are documented separately in the Method.

September 2026

Public Check method, evidence and provider context

Refined ThreatScope Check as a clearer bounded triage instrument while preserving its point-in-time, non-scoring approach.

  • Aligned results and Method around four assessment areas, with Certificate Transparency as supporting context and clearer evidence, coverage and collection-limit presentation.
  • Introduced Provider Resolution and the versioned Provider Catalogue for bounded DNS hosting, inbound mail and SPF associations outside posture calculations.
  • Clarified independent stewardship and moved feedback, corrections, privacy and security contact to native ThreatScope Check channels.
  • Preserved API compatibility 3.2, evidence contract 1.0, stateless /api/signals, and no monitoring, accounts or saved lookup history.

June 2026

Public trust-signal refresh

Refreshed the public experience and clarified how visible trust signals are presented and interpreted.

  • Improved summary hierarchy and plain-English interpretation.
  • Clarified evidence, method and limitation language.
  • Added supporting public pages for Method, Privacy, Terms and change history.
  • Kept the service point-in-time, stateless and without accounts or saved lookup history.

Earlier 2026

Third-generation public Check foundation

Established the current direction as a lightweight public domain trust-signal tool with live checks, plain-English output and no account requirement.