ThreatScope Check Trust signals for the public internet

Privacy

ThreatScope Check privacy notice

How submitted domains, public Provider Catalogue downloads, operational data, public data sources and correspondence are handled for ThreatScope Check.

Last updated
October 2026

In plain English

  • You can run a ThreatScope Check without creating an account.
  • The domain you enter is used to run the live check.
  • ThreatScope Check does not intentionally save a history of checks or build profiles from submitted domains.
  • Messages and supporting evidence you choose to send are handled separately from domain checks. They may be kept where reasonably needed for research, corrections or follow-up.
  • You can download public Provider Catalogue releases without an account. The systems delivering them may still process basic request information.
  • The services that run ThreatScope Check may process basic request information for security, reliability and abuse prevention.
  • ThreatScope Check does not use advertising cookies, behavioural tracking cookies or third-party marketing tags.

Stewardship and operations

ThreatScope Check is owned and stewarded by Bryan Chetcuti.

The Vigo Group may provide operational services involved in delivering or administering ThreatScope Check. Operational support does not change project ownership or stewardship.

Submitted domains

Submitted domains are used to run the live check. ThreatScope Check does not create user accounts, maintain lookup history or intentionally profile submitted domains, but operational infrastructure such as Cloudflare may process request metadata for security, reliability and abuse prevention.

Provider Catalogue downloads

Released Provider Catalogue artefacts are public static files and can be retrieved without creating an account or using the protected Provider Registry. ThreatScope Check does not require a consumer identity or intentionally maintain per-consumer adoption records for those downloads. As with other site requests, operational infrastructure such as Cloudflare may process normal request metadata for delivery, caching, security, reliability and abuse prevention.

If another service vendors, mirrors or otherwise processes a catalogue release after retrieval, that service’s handling of its own users, observations, logs or other data is outside this privacy notice.

See the Provider Catalogue for the public consumption model.

Correspondence

If you use the Contact & feedback form or email a ThreatScope Check contact address, the information you choose to provide is used to review the submission, respond where appropriate, investigate issues, maintain the Provider Catalogue, improve documentation or protect the service.

The contact form routes correspondence to ThreatScope Check-controlled email addresses. It does not intentionally store separate copies of messages in a database or log message contents. Once delivered, correspondence may be retained in email systems for as long as reasonably necessary for review, follow-up, project administration, security or record-keeping.

If you submit a Provider Catalogue reference, correction or research evidence, relevant technical information and public sources may inform retained review records or a later governed catalogue release. Public source references may be cited after independent review. Your original message and contact details are not automatically made public; submitting evidence does not itself create a provider match.

Correspondence is not published automatically. Please do not include passwords, credentials, private keys, confidential system information or other sensitive material. For a security concern that may require sensitive exchange, begin with security@threatscopecheck.com.

Analytics

ThreatScope Check may use privacy-preserving operational analytics to understand service availability, usage volume, errors and abuse patterns. These are not used to create user profiles.

Cookies and tracking

ThreatScope Check does not use advertising cookies, behavioural tracking cookies or third-party marketing tags. Essential security or infrastructure cookies may be used if required to operate or protect the service.

Public and third-party data sources

When you run a check, ThreatScope Check may query public DNS, web, mail and registration data sources to produce the result. These checks are performed against public domain-layer information. The operators of those public or third-party systems may receive normal technical request information as part of responding to those checks.

See the method page for more context on public signal areas and limits.

Retention

ThreatScope Check does not intentionally maintain lookup history or per-consumer Provider Catalogue adoption records. Operational logs, including ordinary requests for public catalogue artefacts, may be retained for limited periods for delivery, security, reliability and abuse prevention. Correspondence is separate from lookup activity and may be retained as described above.