Detect LiveBooks

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

• DOM selectors

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

• div

Establishes

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

Does not establish

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

Can PluginView detect LiveBooks without logging in?

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

What category is LiveBooks?

LiveBooks is classified under Page builders in the PluginView directory.

How many fingerprint rules cover LiveBooks?

This reference currently tracks 1 fingerprint rule across dom selectors. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses LiveBooks?

Illustrative public indicators for LiveBooks include div. A live scan may match additional proprietary rules beyond these examples.