Detect Kerberos

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

• Response headers

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

• www-authenticate: Kerberos

Establishes

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

Does not establish

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

Can PluginView detect Kerberos without logging in?

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

What category is Kerberos?

Kerberos is classified under Security in the PluginView directory.

How many fingerprint rules cover Kerberos?

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 Kerberos?

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