Detect SiteSpect

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

• Script sources
• JavaScript globals

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

• __ssobj/core.js
• ss_dom_var

Establishes

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

Does not establish

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

Can PluginView detect SiteSpect without logging in?

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

What category is SiteSpect?

SiteSpect is classified under A/B Testing in the PluginView directory.

How many fingerprint rules cover SiteSpect?

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

What public signals suggest a site uses SiteSpect?

Illustrative public indicators for SiteSpect include __ssobj/core.js; ss_dom_var. A live scan may match additional proprietary rules beyond these examples.