Detect Sardine

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

• Script sources

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

• api.sardine.ai

Establishes

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

Does not establish

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

Can PluginView detect Sardine without logging in?

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

What category is Sardine?

Sardine is classified under Security in the PluginView directory.

How many fingerprint rules cover Sardine?

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

Illustrative public indicators for Sardine include api.sardine.ai. A live scan may match additional proprietary rules beyond these examples.