Detect Weblate

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

• Response headers

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

• content-security-policy: .weblate.org

Establishes

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

Does not establish

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

Can PluginView detect Weblate without logging in?

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

What category is Weblate?

Weblate is classified under Translation in the PluginView directory.

How many fingerprint rules cover Weblate?

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

Illustrative public indicators for Weblate include content-security-policy: .weblate.org. A live scan may match additional proprietary rules beyond these examples.