Detect Contentful

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

• Response headers
• HTML markup
• Inline scripts

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

• server: Contentful Images API
• x-contentful-request-id
• <assetsdownloadsimagesvideos.ct?fassets.netcontentful.com
• .ctfassets.net

Establishes

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

Does not establish

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

Can PluginView detect Contentful without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Contentful — typically response headers, html markup, inline scripts. It does not bypass authentication or paywalls.

What category is Contentful?

Contentful is classified under CMS in the PluginView directory.

How many fingerprint rules cover Contentful?

This reference currently tracks 4 fingerprint rules across response headers, html markup, inline scripts. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Contentful?

Illustrative public indicators for Contentful include server: Contentful Images API; x-contentful-request-id; <assetsdownloadsimagesvideos.ct?fassets.netcontentful.com. A live scan may match additional proprietary rules beyond these examples.