Detect Aspio

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

• Script sources

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

• aspio-io-customer/public/js/aspio-io-customer-public.js

Establishes

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

Does not establish

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

Can PluginView detect Aspio without logging in?

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

What category is Aspio?

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

How many fingerprint rules cover Aspio?

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 Aspio?

Illustrative public indicators for Aspio include aspio-io-customer/public/js/aspio-io-customer-public.js. A live scan may match additional proprietary rules beyond these examples.