Can PluginView detect OneSignal Web Push without logging in?

Yes. PluginView only reads publicly accessible responses when checking for OneSignal Web Push — typically vendor endpoints. It does not bypass authentication or paywalls.

What category is OneSignal Web Push?

OneSignal Web Push is classified under Marketing, CDP, Email & Push in the PluginView directory.

How many fingerprint rules cover OneSignal Web Push?

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

What public signals suggest a site uses OneSignal Web Push?

Illustrative public indicators for OneSignal Web Push include cdn.onesignal.com/sdks; onesignal.com/api/v1. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting OneSignal Web Push?

For OneSignal Web Push, start with: All pages; initialize push.

Detect OneSignal Web Push

Marketing, CDP, Email & Push

PluginView detects OneSignal Web Push, a Marketing, CDP, Email & Push, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with OneSignal Web Push include cdn.onesignal.com/sdks, onesignal.com/api/v1. The listed vendor-controlled browser component was present and active on the scanned page at scan time. Full fingerprint rules remain proprietary; this page summarizes the signal classes and example indicators used for identification.

Detection looks at vendor endpoints across 2 fingerprint rules among the site's public responses.

Websites using OneSignal Web Push

Loading website list…

Signal classes

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

Vendor endpoints

Example public indicators for OneSignal Web Push

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

cdn.onesignal.com/sdks
onesignal.com/api/v1

What a detection means

Establishes: The listed vendor-controlled browser component was present and active on the scanned page at scan time.
Does not establish: It does not prove a sitewide installation, current commercial contract, backend-only use, exclusive use, or production transaction volume.

Minimum proof rule

Observe a live browser request, loaded script, or iframe to the listed unique vendor endpoint. Source-text-only matches do not qualify.

Best pages to check: All pages; initialize push

How to check a site for OneSignal Web Push

1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest OneSignal Web Push signals (prefer: All pages; initialize push).
2. PluginView reads only public responses (vendor endpoints) and scores them against the OneSignal Web Push signature set (2 rules).
3. Review the confidence score and text explanation for OneSignal Web Push on the results page.

FAQ: detecting OneSignal Web Push

Can PluginView detect OneSignal Web Push without logging in?: Yes. PluginView only reads publicly accessible responses when checking for OneSignal Web Push — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is OneSignal Web Push?: OneSignal Web Push is classified under Marketing, CDP, Email & Push in the PluginView directory.
How many fingerprint rules cover OneSignal Web Push?: This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.
What public signals suggest a site uses OneSignal Web Push?: Illustrative public indicators for OneSignal Web Push include cdn.onesignal.com/sdks; onesignal.com/api/v1. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting OneSignal Web Push?: For OneSignal Web Push, start with: All pages; initialize push.