Detect Infolinks

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

• JavaScript globals

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

• infolinks_pid
• infolinks_wsid

Establishes

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

Does not establish

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

Can PluginView detect Infolinks without logging in?

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

What category is Infolinks?

Infolinks is classified under Advertising in the PluginView directory.

How many fingerprint rules cover Infolinks?

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

What public signals suggest a site uses Infolinks?

Illustrative public indicators for Infolinks include infolinks_pid; infolinks_wsid. A live scan may match additional proprietary rules beyond these examples.