Detect Strands

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

• Script sources

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

• .strands.com

Establishes

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

Does not establish

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

Can PluginView detect Strands without logging in?

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

What category is Strands?

Strands is classified under Personalisation in the PluginView directory.

How many fingerprint rules cover Strands?

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 Strands?

Illustrative public indicators for Strands include .strands.com. A live scan may match additional proprietary rules beyond these examples.