Detect Absorb

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

• Cookies
• JavaScript globals

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

• _absorb_ui_session
• AbsorbLMS

Establishes

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

Does not establish

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

Can PluginView detect Absorb without logging in?

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

What category is Absorb?

Absorb is classified under LMS in the PluginView directory.

How many fingerprint rules cover Absorb?

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

What public signals suggest a site uses Absorb?

Illustrative public indicators for Absorb include _absorb_ui_session; AbsorbLMS. A live scan may match additional proprietary rules beyond these examples.