Detect Viloud

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

• DOM selectors
• Inline scripts

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

• iframe
• app.viloud.tv

Establishes

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

Does not establish

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

Can PluginView detect Viloud without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Viloud — typically dom selectors, inline scripts. It does not bypass authentication or paywalls.

What category is Viloud?

Viloud is classified under Livestreaming in the PluginView directory.

How many fingerprint rules cover Viloud?

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

What public signals suggest a site uses Viloud?

Illustrative public indicators for Viloud include iframe; app.viloud.tv. A live scan may match additional proprietary rules beyond these examples.