Detect Naver Analytics

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

• Script sources

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

• wcs.naver.net/wcslog.js

Establishes

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

Does not establish

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

Can PluginView detect Naver Analytics without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Naver Analytics — typically script sources. It does not bypass authentication or paywalls.

What category is Naver Analytics?

Naver Analytics is classified under Analytics in the PluginView directory.

How many fingerprint rules cover Naver Analytics?

This reference currently tracks 1 fingerprint rule across script sources. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Naver Analytics?

Illustrative public indicators for Naver Analytics include wcs.naver.net/wcslog.js. A live scan may match additional proprietary rules beyond these examples.