Site Behavior Lab
Site

www.canada.ca

Baseline visit
Requested address
https://www.canada.ca/…
Report ID
20261118-46ce582c512fe02eeb84c5e1ac58d9ff
Evidence SHA-256
aa82f0b74b797ec22b73510b44520bffdf9a8a9e62226f7fabf87f0fa0c6b138
Scanner
playwright-chromium

canada.ca's retained request log includes 1 distinct catalogued tracking-related service.

Where this page's requests went

The No blocking visit. One mark is one request row in the retained log.

www.canada.ca itselfat least 60 retained requestsrequests that stayed on the site
Catalogued servicesat least 10 retained requests1 name: Adobe 10
Hosts the catalog does not nameat least 9 retained requests5 hosts; the catalog cannot say who operates them
Not measuredabsence here is not evidence of absence
  • Other pages on this site
  • Signed-in visitors, other browsers and other regions
  • Anything that loads only after interaction or consent
  • Services the catalog does not name
  • Checks with incomplete evidence
  • one request on record, same site
  • one request on record, cross-site
  • the count is a lower bound; more may exist
  • not measured

Retained rows include Adobe (1 recorded responses): at least 19 retained requests went to at least 8 retained cross-site domains. This report does not record which requests came during the typing test. Catalog labels do not prove the purpose of an individual request or that profiling occurred.

≥1tracking-service entity retained
≥19cross-site requests
2third-party cookie records

Worth checking

Bottom line: this visit has signals worth checking

The scan observed signals a non-expert should not have to decode from raw request tables. Some activity evidence was also incomplete: request counts are retained lower bounds.

This failed or incomplete evidence is not ranked against corpus percentiles; positive signals remain visible as lower bounds. Details

The cards below translate the evidence into plain language. The request log, domain table, and methodology remain below for verification.

At least 79 retained requests observed in one controlled visit.

What was checked

Page
https://www.canada.ca/…
When
Nov 18, 2026, 5:41 PM UTC
Setup
Both visits used headless Chromium in a desktop window of 1440 × 980, with en-US language and UTC time zone. Both ran from a GitHub Actions Ubuntu runner; the network region was not recorded. Neither sent the Global Privacy Control (GPC) signal.
Visits
Two visits configured to differ in Brave-list blocking: No blocking and Brave-list blocking.
Interactions
Typed a made-up test value into 1 form field in each visit, never submitting the form. No scrolling, clicking or consent interaction.
Outcome
Both visits completed, but some evidence was cut short.

What these visits could not see

  • Other pages on this site. Only the requested page's activity was recorded. The privacy policy was opened only to read its text, and none of its activity was recorded.
  • Signed-in visitors, other browsers and other regions. Both visits were automated, from a fixed en-US / UTC profile. Sites can behave differently for real users, browsers, regions, accounts, or network locations.
  • Anything that loads only after interaction or consent. Trackers that load that late are not observed, so counts are a lower bound.
  • Services the catalog does not name. Service labels use a US-biased hand-curated catalog, so regional services may be under-labeled.
  • Checks with incomplete evidence. In both visits: Brave Shields matches, the privacy policy check, third-party services, named platforms, Google Analytics remarketing, advertising pixels and the consent banner. Each linked card states what was retained.

Worth checking

At least 10 retained requests matched Brave Shields filter lists

At least 10 retained requests matched the default filter lists of Brave Shields, the ad and tracker blocker built into the Brave browser, while loading normally.

Blocking can also prevent follow-on requests, so this number is neither a measured block count nor what a Brave visit would block. Details

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. This is Site Behavior Lab's list-based simulation, which applies every list to the site's own requests too. Brave's default Standard setting skips most of these lists for such requests, so its results can differ.

The hand-curated service catalog separately matched at least 10 retained request rows in this visit.Show matched requests

Context

This Shields comparison is not conclusive

The "No blocking" visit had one or more requests refused by the scanner's own network guard, so its request evidence is incomplete. The "Brave-list blocking" visit had one or more requests refused by the scanner's own network guard, so its request evidence is incomplete.

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.

2 disqualifying conditions named by the report's claim policy.Show matched requests

Context

Privacy policy read; it made no statement this scan can check

None of the statements this scan knows how to check appear in the policy text. As a result, nothing was compared against this visit's evidence (1 of 1 observed tracking company named in the policy). That is a limit of the automated check, not a finding about the site either way.

Evidence collection was cut short, so this covers only what was recorded before the cutoff. Details

Statements checked automatically: blanket no-cookie claims, third-party-cookie claims, and combined do-not-sell-or-share claims against advertising-pixel identifier fields. Global Privacy Control claims are never checked against request counts, which cannot show whether selling or sharing stopped.

Policy at https://www.canada.ca/en/…; 0 checkable statements matched; 1 of 1 observed tracking company named in the policy.

Context

Catalogued service domains recorded responses during this visit

Adobe appeared in the request log.

A catalog match identifies a maintainer-reviewed service/domain mapping; it does not establish why an individual request occurred, what it carried, or whether profiling happened. Details

Functional catalog labels include analytics / advertising. This scan could not identify 3 of the 8 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site.

At least 19 retained cross-site requests across at least 8 retained third-party hosts. This report does not record which requests came during the typing test.Show third-party requests

Context

Requests were dispatched to major-platform domains the catalog does not carry

This visit dispatched requests to Google domains that the reviewed ownership map names, though the service catalog carries no entry for them.

Asset and font hosts reach this state often: the ownership map establishes who operates the domain, and nothing here establishes the request's purpose or payload. Details

These domains are not counted as catalog-matched requests. Evidence collection was cut short, so this covers only what was recorded before the cutoff.

At least 8 retained cross-site domains seen overall.Show catalog-matched requests

Context

Incomplete evidence: No Google Analytics observed in retained evidence before collection stopped

No Google Analytics request appears in the retained evidence.

Evidence collection was cut short, so this covers only what was recorded before the cutoff. Details

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

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

Context

Third-party cookies were present

2 third-party cookies showed up during the visit.

This report does not retain cookie values or partition keys, so it does not establish whether a cookie was a persistent identifier or could recognize a visitor across sites. Details

The scanner observed cookie metadata whose domain crossed the scanned site's registrable-domain boundary.

21 cookies total in this report.

Look closer

See other visits' cookie counts

Opens this site's history page, which lists the third-party cookie count each of its retained reports recorded.

Context

Fingerprint-like browser APIs were called

1 high-entropy API call appeared in the instrumentation log.

These calls can be legitimate (charts, graphics, media), so the count is observational, not a severity score, and it excludes Web and Service Workers. Details

Top calls: webgl.getParameter.UNMASKED_RENDERER_WEBGL.

1 API family recorded.

Domain evidence

11 recorded domains

These are retained domain rows, not a complete inventory.

The busiest recorded domains of the No blocking visit, with role, request count, request start times and catalog match.
DomainRequestsWhen, 0 to 27.5 sCatalog matchRoleResource types
www.canada.ca35No catalog matchfirst-partydocument, script, stylesheet, image, font, xhr
apps.canada.ca19No catalog matchfirst-partyfetch
cdn.*.*.canada.ca6No catalog matchfirst-partyscript, stylesheet
assets.adobedtm.com5Adobe: analytics / advertisingservicescript
*.gstatic.com4No catalog matchthird-partyfont
*.demdex.net3Adobe: analytics / advertisingservicexhr, document, image
*.*.omtrdc.net2Adobe: analytics / advertisingservicexhr, image
*.go-mpulse.net2No catalog matchthird-partyscript, xhr
*.fontawesome.com1No catalog matchthird-partystylesheet
ajax.googleapis.com1No catalog matchthird-partyscript
*.everesttech.net1No catalog matchthird-partyimage

Raw evidence

Open the interactive evidence explorer

The findings above are built from the stored report. Load the request rows, domains, cookies, storage keys, browser signals, visit phases, charts and CSV export when you want to check them; the versioned report JSON is always available below without this interface.

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
20261118-46ce582c512fe02eeb84c5e1ac58d9ff
Site
www.canada.ca
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: the scanner's own network guard refused one or more requests, which were never sent and have no row, so the request evidence is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
159.0.8154.6
Redaction
not recorded by this schema
Provenance
Exact build and instrument digests were not recorded by this legacy schema.

Variant visit

Started
Run quality
cut short: the scanner's own network guard refused one or more requests, which were never sent and have no row, so the request evidence is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
159.0.8154.6
Redaction
not recorded by this schema
Provenance
Exact build and instrument digests were not recorded by this legacy schema.

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. A study has been recorded for pixel-events and does not support a published rate under the current build. 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 .