Detect Kontent.ai

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

• Response headers
• DOM selectors

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

• content-security-policy: .kc-usercontent.com
• img, link

Establishes

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

Does not establish

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

Can PluginView detect Kontent.ai without logging in?

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

What category is Kontent.ai?

Kontent.ai is classified under CMS in the PluginView directory.

How many fingerprint rules cover Kontent.ai?

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

What public signals suggest a site uses Kontent.ai?

Illustrative public indicators for Kontent.ai include content-security-policy: .kc-usercontent.com; img, link. A live scan may match additional proprietary rules beyond these examples.