Detect Instant.Page

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

• Script sources

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

• instant.page

Establishes

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

Does not establish

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

Can PluginView detect Instant.Page without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Instant.Page — typically script sources. It does not bypass authentication or paywalls.

What category is Instant.Page?

Instant.Page is classified under JavaScript libraries, Performance in the PluginView directory.

How many fingerprint rules cover Instant.Page?

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

What public signals suggest a site uses Instant.Page?

Illustrative public indicators for Instant.Page include instant.page. A live scan may match additional proprietary rules beyond these examples.