Detect WeTravel

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

• Script sources
• DOM selectors

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

• .wetravel.com/
• link

Establishes

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

Does not establish

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

Can PluginView detect WeTravel without logging in?

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

What category is WeTravel?

WeTravel is classified under Ticket booking in the PluginView directory.

How many fingerprint rules cover WeTravel?

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

What public signals suggest a site uses WeTravel?

Illustrative public indicators for WeTravel include .wetravel.com/; link. A live scan may match additional proprietary rules beyond these examples.