Detect Mews

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

• Script sources
• JavaScript globals
• DOM selectors

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

• .mews.li/
• Mews

Establishes

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

Does not establish

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

Can PluginView detect Mews without logging in?

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

What category is Mews?

Mews is classified under Appointment scheduling in the PluginView directory.

How many fingerprint rules cover Mews?

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

What public signals suggest a site uses Mews?

Illustrative public indicators for Mews include .mews.li/; Mews. A live scan may match additional proprietary rules beyond these examples.