Detect RackCache

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

• Response headers

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

• x-rack-cache

Establishes

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

Does not establish

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

A confirmed RackCache match also implies these technologies are present.

Ruby

Can PluginView detect RackCache without logging in?

Yes. PluginView only reads publicly accessible responses when checking for RackCache — typically response headers. It does not bypass authentication or paywalls.

What category is RackCache?

RackCache is classified under Caching in the PluginView directory.

How many fingerprint rules cover RackCache?

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

What public signals suggest a site uses RackCache?

Illustrative public indicators for RackCache include x-rack-cache. A live scan may match additional proprietary rules beyond these examples.