Detect SPNEGO

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

• Response headers

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

• www-authenticate: Negotiate

Establishes

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

Does not establish

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

Can PluginView detect SPNEGO without logging in?

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

What category is SPNEGO?

SPNEGO is classified under Security in the PluginView directory.

How many fingerprint rules cover SPNEGO?

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

What public signals suggest a site uses SPNEGO?

Illustrative public indicators for SPNEGO include www-authenticate: Negotiate. A live scan may match additional proprietary rules beyond these examples.