Detect Lexer

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

• Script sources
• JavaScript globals

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

• tag.lexer.io
• ___lexer_tag

Establishes

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

Does not establish

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

Can PluginView detect Lexer without logging in?

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

What category is Lexer?

Lexer is classified under Customer data platform in the PluginView directory.

How many fingerprint rules cover Lexer?

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

What public signals suggest a site uses Lexer?

Illustrative public indicators for Lexer include tag.lexer.io; ___lexer_tag. A live scan may match additional proprietary rules beyond these examples.