Detect Fortune3

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

• Script sources
• DOM selectors
• HTML markup

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

• cartjs.php?.*&?s=*myfortune3cart.com
• link,link
• <link *href="*//www.fortune3.com/*siterate/rate.cssPowered by <a *href=…

Establishes

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

Does not establish

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

Can PluginView detect Fortune3 without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Fortune3 — typically script sources, dom selectors, html markup. It does not bypass authentication or paywalls.

What category is Fortune3?

Fortune3 is classified under Ecommerce in the PluginView directory.

How many fingerprint rules cover Fortune3?

This reference currently tracks 3 fingerprint rules across script sources, dom selectors, html markup. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Fortune3?

Illustrative public indicators for Fortune3 include cartjs.php?.*&?s=*myfortune3cart.com; link,link; <link *href="*//www.fortune3.com/*siterate/rate.cssPowered by <a *href=…. A live scan may match additional proprietary rules beyond these examples.