Detect IPFS

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

• Response headers

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

• x-cf-ipfs-cache-status
• x-ipfs-datasize
• x-ipfs-gateway-host
• x-ipfs-lb-pop
• x-ipfs-path
• x-ipfs-pop
• x-ipfs-root
• x-ipfs-root-cid

Establishes

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

Does not establish

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

Can PluginView detect IPFS without logging in?

Yes. PluginView only reads publicly accessible responses when checking for IPFS — typically response headers. It does not bypass authentication or paywalls.

What category is IPFS?

IPFS is classified under Network storage in the PluginView directory.

How many fingerprint rules cover IPFS?

This reference currently tracks 9 fingerprint rules across response headers. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses IPFS?

Illustrative public indicators for IPFS include x-cf-ipfs-cache-status; x-ipfs-datasize; x-ipfs-gateway-host. A live scan may match additional proprietary rules beyond these examples.