Detect Securiti

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

• Script sources
• Inline scripts

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

• .securiti.ai

Establishes

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

Does not establish

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

Can PluginView detect Securiti without logging in?

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

What category is Securiti?

Securiti is classified under Security in the PluginView directory.

How many fingerprint rules cover Securiti?

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

What public signals suggest a site uses Securiti?

Illustrative public indicators for Securiti include .securiti.ai. A live scan may match additional proprietary rules beyond these examples.