Detect 6sense

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

• Response headers
• Script sources

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

• content-security-policy: .6sc.co/
• .6sc.co/

Establishes

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

Does not establish

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

Can PluginView detect 6sense without logging in?

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

What category is 6sense?

6sense is classified under Marketing automation, Personalisation in the PluginView directory.

How many fingerprint rules cover 6sense?

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

What public signals suggest a site uses 6sense?

Illustrative public indicators for 6sense include content-security-policy: .6sc.co/; .6sc.co/. A live scan may match additional proprietary rules beyond these examples.