Baseline visit

nodejs.org

Requested addresshttps://nodejs.org/

Jul 14, 2026, 3:24 AM UTC

complete; recorded by the scanner

Scan report ready for nodejs.org: 48 recorded request rows.

Comparison Report

nodejs.org

Recorded final address https://nodejs.org/en
ShareDownloads the No blocking visit's request CSV, source report and correction context in a ZIP. Follows the evidence switcher below.PDF + evidence (opens in a new tab)Downloads a ZIP containing the PDF for every recorded visit, exact source JSON, correction context and file hashes. The scanner renders it on request.

What this actually means

1 request in this visit matched Brave Shields filter lists.

1 request matched while loading normally, out of 44 requests the engine evaluated. Matching identifies traffic the lists would target; it does not establish the purpose or payload of an individual request.

Plain-Language Findings

What this visit means

Unfamiliar terms are defined in the glossary
playwright-chromium

Context

Bottom line: this visit has review-worthy signals

The scan observed signals a non-expert should not have to decode from raw request tables.

The cards below translate the evidence into plain language; severity reflects fixed reference thresholds, not measured population percentiles. The request log, domain table, and methodology remain below for verification.

48 requests observed in one controlled visit.

Context

1 of 44 requests the engine evaluated matched Brave Shields filter lists

1 request matched the default filter lists of Brave Shields, the ad and tracker blocker built into the Brave browser, while loading normally.

Computed with Brave's own ad-block engine and default filter lists in classification mode: matched requests were not blocked by the scanner and remain in this report's observed request counts. Matching shows what Shields would target on this visit's traffic. An actual Shields visit blocks these and also prevents their follow-on requests, so this number is neither a measured block count nor the total effect.

The hand-curated service catalog separately matched 0 request rows in this visit.Show matched requests

Context

This Shields comparison supports no comparable delta

The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching.

The raw request logs of both visits remain below for transparency, but the diff between them supports no claim about what the compared condition changed.

1 disqualifying condition named by the report's claim policy.Show matched requests

Not flagged

No known services matched

This scan did not match any third-party domains to the service catalog or another identity source.

No known operator or catalog entity was matched.

0 cross-site requests across 0 third-party hosts.No third-party domains observed.Show third-party requests

Not flagged

No requests to major-platform domains were recorded

No requests to catalogued Google, Meta, TikTok, X, Microsoft, LinkedIn, or Pinterest domains were observed in this visit.

Major-platform domains were not observed in this single passive visit; interaction-gated requests could still load for real users.

0 cross-site domains seen overall.Show catalog-matched requests

Not flagged

No Google Analytics observed

This visit did not contact Google Analytics.

Neither Google Analytics nor its remarketing sync was observed in this visit.

No google-analytics.com or googletagmanager.com requests.Show catalog-matched requests

Not flagged

No third-party cookies observed

The automated visit did not observe third-party cookies.

This does not prove the site never uses cookies; it means this visit did not observe third-party cookies.

0 cookies total in this report.No third-party cookies observed.

Not flagged

No fingerprint-like API calls observed

The scan did not observe the instrumented high-entropy browser APIs.

This is an observation layer, not proof that fingerprinting is impossible.

0 API families recorded.

Brave Shields Comparison

No blocking and Brave-list blocking: two visits, no comparable metric delta

No blocking: 6,511msBrave-list blocking: 2,950msRan first: No blocking
No metric deltas are comparable across these two visits, so none are shown.
  • Request, cookie, and storage deltas (each visit's own evidence still renders below): The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching.
  • Catalog-matched request and entity deltas (each visit's own evidence still renders below): The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching.
  • Other detector and causal-path deltas (each visit's own evidence still renders below): The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching. The privacy-policy detector's status differed between the two visits, so their numbers measure different things.
  • The Shields-number delta (each visit's own evidence still renders below): The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching. The two visits measured different Shields quantities (filter-list matches vs engine-blocked requests), which must never share a delta.
  • Fingerprinting deltas (each visit's own evidence still renders below): At least one visit did not complete the fingerprint measurement, so no exact cross-visit delta is shown.
  • Ad-pixel deltas (each visit's own evidence still renders below): At least one visit did not complete the pixel measurement, so no exact cross-visit delta is shown.

Measurement limits

3 conditions affect how this evidence reads

Both visits

  • Each visit in this report is one automated, headless Chromium visit from a fixed en-US / UTC profile, with no scrolling, clicking, or consent interaction. Sites can behave differently for real users, browsers, regions, accounts, or network locations.
  • Counts are a lower bound: trackers that load only after interaction or consent, any activity inside Web or Service Workers, and WebSocket traffic are not observed. Service labels use a US-biased hand-curated catalog, so regional services may be under-labeled. Cookie and storage figures are an end-of-visit snapshot, with storage keys read from the top frame only.

Brave-list blocking visit only

  • Brave Shields block simulation was enabled; matching requests were aborted before loading and are not included in request totals.

This versioned report is currently retained in the public corpus. Follow the currently retained site history, repeat the same public route when it is available, or request a transparent evidence correction.

Report ID
20260714-be94cc2d911e26d027950a336147917e
Site
nodejs.org
Latest visit
Schema
v2 schema (r2)
Verify recorded provenance

Baseline visit

Started
Run quality
complete; recorded by the scanner
Scanner
playwright-chromium
Browser
149.0.7827.55
Redaction
version 4
Methodology
shields-request-context-v2-adblock-rust-0.13.0-request-method-v1+phase-kernel-v1+boundary-state-v1+consent-r2-v1+resource-budget-v1
Detector registry
node-detectors-v21961b4197b649b6eb8028f95a9f2f6b28973b7427178b23e661017da7ed0c7c4
Tracker catalog digest
b7d4991063310a81b56342ca7ad949723e785704326179e1658335d7af2f88cf
Brave-list instrument
engine adblock-rust-0.13.017d246aca749766d24266f98061bb05f9d88182529285a3472e57045663261a9
Normalization
redaction-v3+allowlists-v2:042fbfccf7b914479b7100002c5f709b54314606840c4dde50fb2368e23c30e8+public-string-policy-v2:74f1170bbf38a2f85629fa612c01f5da3c0ab1d8f0042f4082eef21815db868c+tldts@7.4.3+node-evidence-policy-v1+v3-to-v4-ip-port-title@1

Variant visit

Started
Run quality
complete; recorded by the scanner
Scanner
playwright-chromium
Browser
149.0.7827.55
Redaction
version 4
Methodology
shields-request-context-v2-adblock-rust-0.13.0-request-method-v1+phase-kernel-v1+boundary-state-v1+consent-r2-v1+resource-budget-v1
Detector registry
node-detectors-v21961b4197b649b6eb8028f95a9f2f6b28973b7427178b23e661017da7ed0c7c4
Tracker catalog digest
b7d4991063310a81b56342ca7ad949723e785704326179e1658335d7af2f88cf
Brave-list instrument
engine adblock-rust-0.13.017d246aca749766d24266f98061bb05f9d88182529285a3472e57045663261a9
Normalization
redaction-v3+allowlists-v2:042fbfccf7b914479b7100002c5f709b54314606840c4dde50fb2368e23c30e8+public-string-policy-v2:74f1170bbf38a2f85629fa612c01f5da3c0ab1d8f0042f4082eef21815db868c+tldts@7.4.3+node-evidence-policy-v1+v3-to-v4-ip-port-title@1

Recorded provenance is self-reported measurement metadata, not a cryptographic attestation. The public versioned report JSON contains the retained public evidence; see the methodology for interpretation and retention limits.

This report covers what the scanner measures, not everything a site can do. 17 browser surfaces are not instrumented at all (Every page except the one that was scanned; Anything that only loads after scrolling or interaction; Why a request happened, as a causal chain; and 14 others), 3 capabilities are declined by policy, and 3 are outside what any single visit can see. Their absence from this report is not evidence that they did not occur. Read the published coverage boundary.

Detector accuracy is unmeasured. No calibration study currently publishes a precision or recall for the detectors on this page, so a detector match here is a recorded observation, not a calibrated classification. How detector accuracy is measured.

Approved use boundary: This report is investigative evidence that requires independent corroboration. It is not a standalone legal determination and not the sole exhibit in a legal proceeding. Recorded in this project's release manifest on .