Can PluginView detect New Relic Browser without logging in?

Yes. PluginView only reads publicly accessible responses when checking for New Relic Browser — typically vendor endpoints. It does not bypass authentication or paywalls.

What category is New Relic Browser?

New Relic Browser is classified under Analytics, Product Intelligence & Monitoring in the PluginView directory.

How many fingerprint rules cover New Relic Browser?

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 New Relic Browser?

Illustrative public indicators for New Relic Browser include js-agent.newrelic.com; bam.nr-data.net. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting New Relic Browser?

For New Relic Browser, start with: All pages; interact and wait.

Detect New Relic Browser

Analytics, Product Intelligence & Monitoring

PluginView detects New Relic Browser, a Analytics, Product Intelligence & Monitoring, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with New Relic Browser include js-agent.newrelic.com, bam.nr-data.net. 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 New Relic Browser

Loading website list…

Signal classes

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

Vendor endpoints

Example public indicators for New Relic Browser

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

js-agent.newrelic.com
bam.nr-data.net

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; interact and wait

How to check a site for New Relic Browser

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

FAQ: detecting New Relic Browser

Can PluginView detect New Relic Browser without logging in?: Yes. PluginView only reads publicly accessible responses when checking for New Relic Browser — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is New Relic Browser?: New Relic Browser is classified under Analytics, Product Intelligence & Monitoring in the PluginView directory.
How many fingerprint rules cover New Relic Browser?: 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 New Relic Browser?: Illustrative public indicators for New Relic Browser include js-agent.newrelic.com; bam.nr-data.net. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting New Relic Browser?: For New Relic Browser, start with: All pages; interact and wait.