Detect Thrillshare

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

• Inline scripts

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

• .thrillshare.com/

Establishes

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

Does not establish

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

Can PluginView detect Thrillshare without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Thrillshare — typically inline scripts. It does not bypass authentication or paywalls.

What category is Thrillshare?

Thrillshare is classified under CMS in the PluginView directory.

How many fingerprint rules cover Thrillshare?

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

What public signals suggest a site uses Thrillshare?

Illustrative public indicators for Thrillshare include .thrillshare.com/. A live scan may match additional proprietary rules beyond these examples.