Detect HeyLight

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

• JavaScript globals
• DOM selectors

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

• closePagodilModal
• openPagodilModal
• pagodilLang
• pagodilSprintf
• div#heidipay-container, div, div#pagolight-pro-dialog, iframe#heidipay-…

Establishes

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

Does not establish

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

Can PluginView detect HeyLight without logging in?

Yes. PluginView only reads publicly accessible responses when checking for HeyLight — typically javascript globals, dom selectors. It does not bypass authentication or paywalls.

What category is HeyLight?

HeyLight is classified under Buy now pay later in the PluginView directory.

How many fingerprint rules cover HeyLight?

This reference currently tracks 5 fingerprint rules across javascript globals, dom selectors. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses HeyLight?

Illustrative public indicators for HeyLight include closePagodilModal; openPagodilModal; pagodilLang. A live scan may match additional proprietary rules beyond these examples.