Detect TableCheck

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

• Script sources
• DOM selectors

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

• tc_widget.js
• form

Establishes

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

Does not establish

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

Can PluginView detect TableCheck without logging in?

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

What category is TableCheck?

TableCheck is classified under Reservations & delivery in the PluginView directory.

How many fingerprint rules cover TableCheck?

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

What public signals suggest a site uses TableCheck?

Illustrative public indicators for TableCheck include tc_widget.js; form. A live scan may match additional proprietary rules beyond these examples.