Detect LiveZilla

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

• JavaScript globals
• DOM selectors

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

• lz_chat_execute
• lz_code_id:
• lz_tracking_set_widget_visibility
• #lz_overlay_chat

Establishes

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

Does not establish

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

Can PluginView detect LiveZilla without logging in?

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

What category is LiveZilla?

LiveZilla is classified under Live chat in the PluginView directory.

How many fingerprint rules cover LiveZilla?

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

What public signals suggest a site uses LiveZilla?

Illustrative public indicators for LiveZilla include lz_chat_execute; lz_code_id:; lz_tracking_set_widget_visibility. A live scan may match additional proprietary rules beyond these examples.