Detect Human Presence

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

• Script sources

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

• .*.humanpresence.ioapp/

Establishes

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

Does not establish

A sitewide install of Human Presence, an active vendor contract, exclusive use, or that Human Presence 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 Human Presence signals.
2. 2. PluginView reads only public responses (script sources) and scores them against the Human Presence signature set (1 rules).
3. 3. Review the confidence score and text explanation for Human Presence on the results page.

Can PluginView detect Human Presence without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Human Presence — typically script sources. It does not bypass authentication or paywalls.

What category is Human Presence?

Human Presence is classified under Security in the PluginView directory.

How many fingerprint rules cover Human Presence?

This reference currently tracks 1 fingerprint rule across script sources. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Human Presence?

Illustrative public indicators for Human Presence include .*.humanpresence.ioapp/. A live scan may match additional proprietary rules beyond these examples.