Detect Finsweet

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

• Script sources
• JavaScript globals

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

• cdn.finsweet.com
• FinsweetAttributes.load
• FinsweetConsentPro

Establishes

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

Does not establish

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

Can PluginView detect Finsweet without logging in?

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

What category is Finsweet?

Finsweet is classified under Page builders in the PluginView directory.

How many fingerprint rules cover Finsweet?

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

What public signals suggest a site uses Finsweet?

Illustrative public indicators for Finsweet include cdn.finsweet.com; FinsweetAttributes.load; FinsweetConsentPro. A live scan may match additional proprietary rules beyond these examples.