Detect CargoServer

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

• Meta tags

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

• application-name: CargoServer

Establishes

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

Does not establish

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

Can PluginView detect CargoServer without logging in?

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

What category is CargoServer?

CargoServer is classified under Remote access in the PluginView directory.

How many fingerprint rules cover CargoServer?

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

What public signals suggest a site uses CargoServer?

Illustrative public indicators for CargoServer include application-name: CargoServer. A live scan may match additional proprietary rules beyond these examples.