Detect Comms

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

• Meta tags
• Script sources

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

• generator: comms.dev
• cdn.startcomms.com

Establishes

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

Does not establish

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

Can PluginView detect Comms without logging in?

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

What category is Comms?

Comms is classified under Ecommerce in the PluginView directory.

How many fingerprint rules cover Comms?

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

What public signals suggest a site uses Comms?

Illustrative public indicators for Comms include generator: comms.dev; cdn.startcomms.com. A live scan may match additional proprietary rules beyond these examples.