What teams put it in front of.
The same measurement answers all three. What changes is which finding you act on and whether a contradicted visitor is asked to clear a device.
One measurement, three questions
Heretic does not ship a separate product per problem. A session is measured once: the transport stack the kernel built, the TLS and HTTP construction the client library built, whether a browser claiming HTTP/3 ever attempts QUIC, the round trip against the distance the claimed timezone implies, what the processor and GPU deliver under a fixed workload, and whether the page's own object graph has been rewritten.
What differs between these three problems is which findings matter to you and what you do next. A scraper is worth refusing outright. A registration that looks like a device you have already cleared is worth a ceremony. A trial signup from an anti-detect browser might be worth allowing and watching.
All three get the same honest report, because the policy is yours.
Run it against this browser.
The live probe measures the browser you are reading this in and shows the claims and the measurements side by side, with every finding it produced.