Detect Magic UI

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

• DOM selectors

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

• iframe
• a > video

Establishes

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

Does not establish

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

Can PluginView detect Magic UI without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Magic UI — typically dom selectors. It does not bypass authentication or paywalls.

What category is Magic UI?

Magic UI is classified under UI frameworks in the PluginView directory.

How many fingerprint rules cover Magic UI?

This reference currently tracks 2 fingerprint rules across dom selectors. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Magic UI?

Illustrative public indicators for Magic UI include iframe; a > video. A live scan may match additional proprietary rules beyond these examples.