Detect ModiFace

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

• Response headers
• Script sources
• JavaScript globals
• DOM selectors

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

• content-security-policy: .modiface.com
• .modiface.com/
• initModiface
• iframe

Establishes

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

Does not establish

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

Can PluginView detect ModiFace without logging in?

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

What category is ModiFace?

ModiFace is classified under Augmented reality in the PluginView directory.

How many fingerprint rules cover ModiFace?

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

What public signals suggest a site uses ModiFace?

Illustrative public indicators for ModiFace include content-security-policy: .modiface.com; .modiface.com/; initModiface. A live scan may match additional proprietary rules beyond these examples.