Detect Borderfree

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

• Cookies
• Script sources
• JavaScript globals

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

• bfx.apiKey::
• bfx.country:: x
• bfx.language: x
• bfx.logLevel: x
• global.prd.borderfree.com
• wm.prd.borderfree.com
• bfx-objects.prd.borderfree.com
• bfx._apiKey

Establishes

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

Does not establish

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

Can PluginView detect Borderfree without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Borderfree — typically cookies, script sources, javascript globals. It does not bypass authentication or paywalls.

What category is Borderfree?

Borderfree is classified under Cross border ecommerce in the PluginView directory.

How many fingerprint rules cover Borderfree?

This reference currently tracks 9 fingerprint rules across cookies, script sources, javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Borderfree?

Illustrative public indicators for Borderfree include bfx.apiKey::; bfx.country:: x; bfx.language: x. A live scan may match additional proprietary rules beyond these examples.