Detect Citizen Space

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

• Script sources
• JavaScript globals
• DOM selectors

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

• static/vendor/dlb-admin-ui/
• cs_embedded_content

Establishes

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

Does not establish

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

Can PluginView detect Citizen Space without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Citizen Space — typically script sources, javascript globals, dom selectors. It does not bypass authentication or paywalls.

What category is Citizen Space?

Citizen Space is classified under CMS in the PluginView directory.

How many fingerprint rules cover Citizen Space?

This reference currently tracks 3 fingerprint rules across script sources, javascript globals, dom selectors. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Citizen Space?

Illustrative public indicators for Citizen Space include static/vendor/dlb-admin-ui/; cs_embedded_content. A live scan may match additional proprietary rules beyond these examples.