Detect TableFever

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

• Script sources
• Inline scripts

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

• .tablefever.com

Establishes

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

Does not establish

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

Can PluginView detect TableFever without logging in?

Yes. PluginView only reads publicly accessible responses when checking for TableFever — typically script sources, inline scripts. It does not bypass authentication or paywalls.

What category is TableFever?

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

How many fingerprint rules cover TableFever?

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

What public signals suggest a site uses TableFever?

Illustrative public indicators for TableFever include .tablefever.com. A live scan may match additional proprietary rules beyond these examples.