Detect Go Instore

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

• Response headers
• Script sources
• JavaScript globals

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

• content-security-policy: .goinstore.com
• gis.goinstore.com/
• GISAPP.videoJsCtrl
• gisAppLib.postRobot

Establishes

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

Does not establish

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

Can PluginView detect Go Instore without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Go Instore — typically response headers, script sources, javascript globals. It does not bypass authentication or paywalls.

What category is Go Instore?

Go Instore is classified under Livestreaming in the PluginView directory.

How many fingerprint rules cover Go Instore?

This reference currently tracks 4 fingerprint rules across response headers, script sources, javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Go Instore?

Illustrative public indicators for Go Instore include content-security-policy: .goinstore.com; gis.goinstore.com/; GISAPP.videoJsCtrl. A live scan may match additional proprietary rules beyond these examples.