Detect Makaira

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

• Response headers
• Script sources

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

• content-security-policy: .makaira.io
• x-makaira-scenario
• .makaira.io

Establishes

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

Does not establish

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

Can PluginView detect Makaira without logging in?

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

What category is Makaira?

Makaira is classified under Ecommerce frontends in the PluginView directory.

How many fingerprint rules cover Makaira?

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

What public signals suggest a site uses Makaira?

Illustrative public indicators for Makaira include content-security-policy: .makaira.io; x-makaira-scenario; .makaira.io. A live scan may match additional proprietary rules beyond these examples.