Detect Chicago Boss

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

• Cookies

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

• _boss_session
• book_like_a_boss_session

Establishes

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

Does not establish

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

A confirmed Chicago Boss match also implies these technologies are present.

Erlang

Can PluginView detect Chicago Boss without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Chicago Boss — typically cookies. It does not bypass authentication or paywalls.

What category is Chicago Boss?

Chicago Boss is classified under Web frameworks in the PluginView directory.

How many fingerprint rules cover Chicago Boss?

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

What public signals suggest a site uses Chicago Boss?

Illustrative public indicators for Chicago Boss include _boss_session; book_like_a_boss_session. A live scan may match additional proprietary rules beyond these examples.