Detect HetrixTools

PluginView evaluates public page signals in these classes when identifying HetrixTools. Individual fingerprint rule bodies are proprietary and are not published.

• Response headers
• Script sources
• JavaScript globals

Illustrative indicators derived from public catalog metadata for HetrixTools. A live scan may match additional proprietary rules beyond these examples.

• content-security-policy: .hetrixtools.com
• .hetrixtools.com/
• htoolz

Establishes

One or more public signals on the scanned page matched a known HetrixTools signature (3 rules) at the time of the scan.

Does not establish

A sitewide install of HetrixTools, an active vendor contract, exclusive use, or that HetrixTools is still in place today.

1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest HetrixTools signals.
2. 2. PluginView reads only public responses (response headers, script sources, javascript globals) and scores them against the HetrixTools signature set (3 rules).
3. 3. Review the confidence score and text explanation for HetrixTools on the results page.

Can PluginView detect HetrixTools without logging in?

Yes. PluginView only reads publicly accessible responses when checking for HetrixTools — typically response headers, script sources, javascript globals. It does not bypass authentication or paywalls.

What category is HetrixTools?

HetrixTools is classified under Issue trackers in the PluginView directory.

How many fingerprint rules cover HetrixTools?

This reference currently tracks 3 fingerprint rules across response headers, script sources, javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses HetrixTools?

Illustrative public indicators for HetrixTools include content-security-policy: .hetrixtools.com; .hetrixtools.com/; htoolz. A live scan may match additional proprietary rules beyond these examples.