Detect AfterShip

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

• JavaScript globals

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

• aftership.__VERSION__:

Establishes

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

Does not establish

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

Can PluginView detect AfterShip without logging in?

Yes. PluginView only reads publicly accessible responses when checking for AfterShip — typically javascript globals. It does not bypass authentication or paywalls.

What category is AfterShip?

AfterShip is classified under Fulfilment in the PluginView directory.

How many fingerprint rules cover AfterShip?

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

What public signals suggest a site uses AfterShip?

Illustrative public indicators for AfterShip include aftership.__VERSION__:. A live scan may match additional proprietary rules beyond these examples.