Detect Sanity.io

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

• Response headers
• Script sources
• DOM selectors

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

• content-security-policy: cdn.sanity.io
• x-sanity-shard
• cdn.sanity.io
• img,img,video,source,source,track

Establishes

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

Does not establish

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

Can PluginView detect Sanity.io without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Sanity.io — typically response headers, script sources, dom selectors. It does not bypass authentication or paywalls.

What category is Sanity.io?

Sanity.io is classified under CMS in the PluginView directory.

How many fingerprint rules cover Sanity.io?

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

What public signals suggest a site uses Sanity.io?

Illustrative public indicators for Sanity.io include content-security-policy: cdn.sanity.io; x-sanity-shard; cdn.sanity.io. A live scan may match additional proprietary rules beyond these examples.