Detect pinoox

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

• Cookies
• JavaScript globals

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

• pinoox_session
• pinoox

Establishes

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

Does not establish

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

A confirmed pinoox match also implies these technologies are present.

PHP

Can PluginView detect pinoox without logging in?

Yes. PluginView only reads publicly accessible responses when checking for pinoox — typically cookies, javascript globals. It does not bypass authentication or paywalls.

What category is pinoox?

pinoox is classified under Web frameworks in the PluginView directory.

How many fingerprint rules cover pinoox?

This reference currently tracks 2 fingerprint rules across cookies, javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses pinoox?

Illustrative public indicators for pinoox include pinoox_session; pinoox. A live scan may match additional proprietary rules beyond these examples.