Detect Dice

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

• Script sources
• JavaScript globals
• Inline scripts

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

• widgets.dice.fm
• DiceEventListWidget
• .dice.fm

Establishes

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

Does not establish

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

Can PluginView detect Dice without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Dice — typically script sources, javascript globals, inline scripts. It does not bypass authentication or paywalls.

What category is Dice?

Dice is classified under Ticket booking in the PluginView directory.

How many fingerprint rules cover Dice?

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

What public signals suggest a site uses Dice?

Illustrative public indicators for Dice include widgets.dice.fm; DiceEventListWidget; .dice.fm. A live scan may match additional proprietary rules beyond these examples.