Detect Sucuri

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

• Response headers

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

• x-sucuri-cache:
• x-sucuri-id

Establishes

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

Does not establish

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

Can PluginView detect Sucuri without logging in?

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

What category is Sucuri?

Sucuri is classified under CDN, Security in the PluginView directory.

How many fingerprint rules cover Sucuri?

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

What public signals suggest a site uses Sucuri?

Illustrative public indicators for Sucuri include x-sucuri-cache:; x-sucuri-id. A live scan may match additional proprietary rules beyond these examples.