How to Tell If a Website Uses New Relic
New Relic Browser monitors front-end performance and errors. Detect it via the NREUM global, the inline browser-agent snippet, the nr-data.net beacons and the js-agent.newrelic.com script.
New Relic is one of the longest-established application performance monitoring (APM) platforms, and on the front end it appears as New Relic Browser — an agent that measures real-user page performance, JavaScript errors and interactions. Like other observability tools, it is engineering infrastructure rather than marketing technology, so detecting it is genuinely informative about the team behind a site. The fastest way to confirm New Relic is to type NREUM into the console, or to look for beacons to bam.nr-data.net in the Network tab. This guide walks through every reliable signal, the agent mechanics, the look-alikes to rule out, and what the find means.
What is New Relic Browser?
New Relic is a comprehensive observability platform covering application performance monitoring, infrastructure monitoring, logs, synthetics and more. Its Browser product instruments the front end of a web application to capture how it performs for real visitors: page-load and route-change timings, Core Web Vitals, JavaScript errors and AJAX request performance. That data is correlated in New Relic with back-end transaction traces, so an engineering team can follow a slow or broken experience from the browser all the way down to the database query that caused it.
For detection purposes, the essential point is that New Relic is enterprise engineering infrastructure. It is licensed software, instrumented by developers, and usually part of a broader monitoring deployment. So finding New Relic Browser on a site indicates a real application maintained by an engineering organisation that invests in reliability and performance — typically a mid-to-large company with platform, DevOps or SRE functions. The Browser agent is frequently just the front-end component of a much larger New Relic subscription that also monitors servers, containers and back-end services, so its presence often implies a substantial, contractually committed customer.
How New Relic Browser loads and sends data
New Relic Browser uses a distinctive two-stage loading pattern. First, an inline snippet is injected near the top of the HTML <head> that defines the global NREUM (or window.NREUM) object and seeds it with configuration — the applicationID, the licenseKey, the accountID and various flags. This inline bootstrap begins timing the page immediately, before any external script loads. Second, the snippet asynchronously fetches the main browser agent from js-agent.newrelic.com, typically a file named like nr-<hash>.min.js.
Once the agent is running, it collects performance, error and interaction data and beacons it to New Relic's collection endpoints — bam.nr-data.net and bam-cell.nr-data.net for most accounts, or region-specific hosts like bam.eu01.nr-data.net for EU data residency. These beacons fire on page load, on route changes and as errors occur. The configuration embedded in the NREUM object identifies the exact application and account, so capturing it confirms not just that New Relic is present but which property is being monitored. The inline-NREUM-then-js-agent pattern is unique enough that recognising it makes detection almost instant.
How to tell if a website uses New Relic
Confirm at least two of the following.
1. View the page source. Search the HTML for NREUM, newrelic or nr-data. The inline browser-agent snippet sits near the top of the document and is usually visible even in server-rendered HTML, with the NREUM configuration object spelled out.
2. Use the console. Type NREUM and press Enter. A New Relic Browser page returns the global object containing the configuration and instrumentation. This is the single fastest and clearest check.
3. Check the Network tab. Filter for nr-data or newrelic. You will see the agent download from js-agent.newrelic.com and beacons to bam.nr-data.net (or a regional nr-data.net host). Those beacons are the data-collection calls.
4. Read the configuration. The applicationID, accountID and licenseKey in the NREUM object confirm New Relic and identify the monitored application and account.
5. Confirm the agent host. A request to js-agent.newrelic.com for an nr-<hash>.min.js file is specific to New Relic and corroborates the NREUM global.
What the New Relic signals look like
window.NREUM || (NREUM = {}); NREUM.info = { applicationID: "12345678", licenseKey: "NRJS-abc...", accountID: "987654" };
GET https://js-agent.newrelic.com/nr-spa-1.2.3.min.js
POST https://bam.nr-data.net/events/1/NRJS-abc... (browser beacon)
window.NREUM = { info: {...}, init: {...}, loader_config: {...} }
The combination of the inline NREUM object, the js-agent.newrelic.com agent and beacons to an nr-data.net host is conclusive.
New Relic versus similar tools — avoiding false positives
New Relic Browser sits among observability tools like Datadog RUM, Sentry, Dynatrace, AppDynamics and Elastic APM, so match the exact fingerprint. New Relic uses the NREUM global, the js-agent.newrelic.com agent and nr-data.net beacons; Datadog uses DD_RUM and browser-intake-datadoghq.com; Sentry uses window.Sentry and ingest.sentry.io; Dynatrace uses the dtrum global. The NREUM name is unusual enough that confusion is unlikely once you see it. The main subtlety is that, like all RUM tools, New Relic batches and beacons data frequently, so the steady nr-data.net traffic is normal monitoring rather than a problem. And as with the other enterprise tools, the Browser agent is often one module of a far larger deployment you cannot observe from the page.
How reliable is each New Relic signal?
The NREUM global is definitive — the name is specific to New Relic and the object carries the account and application identifiers. Beacons to an nr-data.net host and the js-agent.newrelic.com agent download are equally conclusive. The configuration values (applicationID, accountID) are unambiguous and identify the property. The weakest signal is a bare "newrelic" string with no NREUM object or beacon traffic, which could be a leftover comment. Because the inline NREUM snippet appears in the initial HTML, New Relic is one of the easier observability tools to confirm even before JavaScript fully executes — the NREUM global plus an nr-data.net beacon settles it.
What a New Relic install reveals about a company
New Relic Browser is a dependable enterprise-engineering signal. It is licensed APM software instrumented by developers, so its presence marks a real application maintained by an engineering organisation that monitors performance and reliability — usually a mid-to-large company with the budget and team to operate an observability platform. Because Browser is typically one part of a wider New Relic subscription covering back-end APM, infrastructure and logs, finding it often implies a significant annual contract and a mature operations practice. If you sell developer tooling, observability or performance products, cloud services, or engineering consulting, a New Relic install identifies a technically serious, budget-bearing account. New Relic also has a long enterprise heritage, so its presence can correlate with established companies and more traditional engineering organisations, in contrast to the start-up lean of some newer tools.
New Relic in a modern engineering stack
New Relic Browser usually sits within a full-stack monitoring setup. The same organisation typically runs New Relic APM agents on its back-end services, infrastructure monitoring on its servers or containers, and log management in the same platform, with Browser providing the front-end view. The application front end is usually a mainstream framework, and you may find New Relic alongside a CDN, a feature-flag system and sometimes a separate error tracker. Larger enterprises occasionally run more than one observability tool during migrations, so do not be surprised to see New Relic and a competitor together. For an auditor, the useful details are the applicationID and accountID, the agent type (the nr-spa agent indicates single-page-app instrumentation, hinting at the front-end architecture), the data region, and which framework the site uses; together these reveal both the scale of the monitoring investment and the engineering shape of the company.
A quick New Relic confirmation walkthrough
Open the site with developer tools on the Console panel and type NREUM — a returned object with an info block confirms New Relic Browser instantly, and you can read the applicationID and accountID straight from it. Switch to the Network tab, filter for nr-data or newrelic, and reload to see the js-agent.newrelic.com agent download and the beacons to bam.nr-data.net. If you prefer the source, view the page HTML and look near the top of the <head> for the inline NREUM snippet. The NREUM global alone is usually conclusive, with the beacon and agent host as corroboration and the configuration providing account-level detail.
A quick New Relic detection checklist
- Type
NREUMin the console; a returned object with aninfoblock is conclusive. - Filter the Network tab for
nr-data; beacons tobam.nr-data.netconfirm collection. - Look near the top of the HTML for the inline
NREUMbootstrap snippet. - Confirm the agent download from
js-agent.newrelic.com. - Read applicationID and accountID from the NREUM configuration.
- Note the agent type (e.g. nr-spa) to infer single-page-app instrumentation.
Detecting New Relic at scale
One page is a quick console check, but auditing many domains for APM tooling — to identify enterprise engineering organisations, say — calls for automation. StackOptic detects New Relic Browser and thousands of other technologies from a real browser, so you can find monitoring-led companies across a list and infer the broader observability stack each implies. For related reading, see checking what JavaScript libraries a website uses and the New Relic technology profile.
Frequently asked questions
What is the fastest way to detect New Relic?
Open the console and type NREUM. New Relic's Browser agent defines this global object at the top of the page, so a returned object confirms it instantly. In the Network tab you can also filter for 'nr-data' to see beacons to bam.nr-data.net, which is New Relic's data-collection endpoint.
What is NREUM?
NREUM stands for New Relic End User Monitoring. It is the global JavaScript object New Relic's Browser agent creates, holding the configuration (application and account identifiers, license key) and the instrumentation hooks. Finding window.NREUM is the single clearest sign that New Relic Browser monitoring is installed.
Where does New Relic send front-end data?
New Relic's Browser agent beacons performance, error and interaction data to bam.nr-data.net and bam-cell.nr-data.net (with EU accounts using bam.eu01.nr-data.net). Seeing requests to an nr-data.net host in the Network tab confirms New Relic is actively collecting data.
Where is the New Relic agent loaded from?
After the inline NREUM bootstrap, the main browser agent is fetched from js-agent.newrelic.com, typically as a file like nr-<hash>.min.js. That script host is specific to New Relic, so a request to js-agent.newrelic.com is a reliable confirmation alongside the NREUM global.
What does using New Relic say about a company?
New Relic is an enterprise application-performance-monitoring platform. Finding its Browser agent indicates an engineering organisation that monitors application performance and reliability, usually a mid-to-large company with a wider New Relic deployment covering back-end APM and infrastructure.
Analyse any website with StackOptic
Get the full technology stack, performance, security and SEO report in seconds — free.
Analyse a websiteRelated articles
How to Tell If a Website Uses Heap
Heap (Heap Analytics) autocaptures product events. Detect it via the cdn.heapanalytics.com script, the global heap object, heapanalytics.com beacons and _hp2 cookies.
How to Tell If a Website Uses Foundation
Foundation (by Zurb) is a responsive front-end framework. Detect it via its grid classes (row/columns, grid-x/cell), data-* component attributes and the foundation.css/js files.
How to Tell If a Website Uses Crisp
Crisp is a developer-friendly, affordable live-chat and messaging tool. Detect it via the client.crisp.chat/l.js script, the window.$crisp object and the CRISP_WEBSITE_ID value.