Detect Makeswift

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

• Response headers
• Inline scripts

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

• access-control-allow-origin: app.makeswift.com
• content-security-policy: app.makeswift.com
• app.makeswift.com

Establishes

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

Does not establish

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

Can PluginView detect Makeswift without logging in?

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

What category is Makeswift?

Makeswift is classified under Page builders in the PluginView directory.

How many fingerprint rules cover Makeswift?

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

What public signals suggest a site uses Makeswift?

Illustrative public indicators for Makeswift include access-control-allow-origin: app.makeswift.com; content-security-policy: app.makeswift.com; app.makeswift.com. A live scan may match additional proprietary rules beyond these examples.