Detect Uplynk

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

• Response headers
• JavaScript globals
• DOM selectors

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

• content-security-policy: .uplynk.com
• UPLYNK
• _uplynk_async_wget2_data
• video, img

Establishes

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

Does not establish

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

Can PluginView detect Uplynk without logging in?

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

What category is Uplynk?

Uplynk is classified under Media servers in the PluginView directory.

How many fingerprint rules cover Uplynk?

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

What public signals suggest a site uses Uplynk?

Illustrative public indicators for Uplynk include content-security-policy: .uplynk.com; UPLYNK; _uplynk_async_wget2_data. A live scan may match additional proprietary rules beyond these examples.