About

What Heretic does

Heretic checks browser claims against browser-integrity tests and connection observations, then returns a verdict with named findings. Your application decides how those findings affect its eligibility rules.

The public demo shows the result for your own browser. The integration documentation explains how to retrieve the result on your server and bind it to the action being protected.

Publication standard

An article needs an original technical contribution: a reproducible experiment, a worked derivation, an implementation explained through its behaviour, or a failure investigated with evidence. The decisive code, observations or reasoning belong in the article itself.

Claims identify their premises and address the counterexamples that matter. Test conditions and results carry enough detail to inspect, and an illustrative example is labelled as an example. Where an article rests on an experiment, its reproduction archive is published alongside it and the archive's SHA-256 is recorded with the article.

Automated tooling assists research and writing. A separate technical review establishes the contribution and checks its evidence before publication. There is no fixed posting schedule. Setup instructions and reference material belong in the product documentation.

Start with a specific problem

• Understand the measurements and their limits.
• Connect signup checks to account creation.
• Review the product's use cases and pricing.

For product questions or article corrections, contact hello@heretic.tech.