Detect Podigee

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

• JavaScript globals
• DOM selectors

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

• podigeePodcastPlayers
• iframe

Establishes

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

Does not establish

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

Can PluginView detect Podigee without logging in?

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

What category is Podigee?

Podigee is classified under Widgets in the PluginView directory.

How many fingerprint rules cover Podigee?

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

What public signals suggest a site uses Podigee?

Illustrative public indicators for Podigee include podigeePodcastPlayers; iframe. A live scan may match additional proprietary rules beyond these examples.