Detect FareHarbor

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

• Script sources
• DOM selectors
• HTML markup

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

• fareharbor.com/embeds/api/
• iframe
• <iframefareharbor

Establishes

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

Does not establish

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

Can PluginView detect FareHarbor without logging in?

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

What category is FareHarbor?

FareHarbor is classified under Widgets, Appointment scheduling in the PluginView directory.

How many fingerprint rules cover FareHarbor?

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 FareHarbor?

Illustrative public indicators for FareHarbor include fareharbor.com/embeds/api/; iframe; <iframefareharbor. A live scan may match additional proprietary rules beyond these examples.