ghosted.← Report examples

Trust & impact / An interactive example

One site.
The trust it carries.

Follow direct suppliers and the resources they introduce.
Then ask what changes if one of those resources is compromised.

NorthlineIllustrative customer report

11 September 2026Example TRUST-MAP-01

Simulated report

Fictional domains and observations. No live scan or provider calls.

What is. What if.

Recorded first and second-order trust, with explicitly assumed breach scenarios. Registered dependencies remain visible; scenarios do not become active findings.

northline.example

Recorded rootFirst orderSecond ordernorthline.examplesupport-service.examplesupport-service.example2 recorded pathstag-service.exampletag-service.example2 recorded pathsframe-assets.exampleframe-assets.example1 recorded pathtelemetry-service.exampletelemetry-service.example1 recorded path
Root, method & coverage
Recorded root
https://northline.example/
Map rules
trust-map-1
Evaluated at
2026-09-11 09:00:00 UTC
Unresolved paths
0
Paths beyond second order
0
  • What is describes the dated, collected state. What if assumes malicious control of a selected resource; it does not claim a breach, execute payloads or change finding priorities.
  • Domain grouping uses public and private suffix boundaries. It is not a verified ownership map; security origins and exact resource URLs remain separate evidence. Registration status applies to the named registration domain, not a hosted tenant account; tenant-name reallocation is not assessed.
  • The map covers assessed references within existing crawl, browser and evidence budgets. Missing bodies, unvisited application states and missing initiators can leave downstream trust unknown. No second-order paths collected does not mean none exist. DNS and MX evidence remains in the mail-routing report; this resource map does not reconstruct unsupported DNS paths.
  • Simulated example: reserved .example domains, fictional observations and no live provider calls.
Resource paths & scenarios (4)

First order / Selected resource

support-service.example

https://support-service.example/widget

What is

Recorded use
Resource response recorded
Registration
support-service.example: No registration exposure observed (UNAVAILABLE)
Impact if control changes
medium
Collected at
2026-09-11 09:00:00 UTC

Simulated resource response. Execution and real visitor activity are not established.

Activation, visibility & dated checks
Activation
The browser loads the embedded content, subject to activation and loading controls.
Tracking / visibility
If a request reaches the endpoint, its operator can see request metadata such as path, query and timing. Client address, referrer and credentials depend on the client, policy and intermediaries. The anonymous scan does not establish exposure of real users or their data.
Registration checked
2026-09-11 09:00:00 UTC
Check valid until
2026-09-11 10:00:00 UTC
Path basis
Each URL relationship has a collected source reference. Order counts external domain boundaries along this path, not navigation hops. Runtime activation remains separate.

What if

Assumed breach. Assume an attacker can replace the selected external resource's response with malicious content. Independent application configuration and controls remain as observed.

The endpoint controls the embedded content. Sandbox, origin boundaries and application messaging determine any effect on the surrounding page.

This path crosses an embedded-document boundary. Code or content normally affects that document; impact on the parent needs additional origin, sandbox or messaging conditions.

Conditions and controls (5)
  • Assumed breach is a scenario, not evidence of compromise. Registration availability does not establish or exclude supplier compromise.
  • Embedded-document sandbox on https://support-service.example/widget: allow-scripts. Retain and validate the applicable restrictions.
  • Frame sandbox attributes: allow-scripts
  • No applicable enforced CSP was collected; other loading and origin controls still apply.
  • The affected application path must remain reachable and use this reference.

Decisions to make

  • Confirm the purpose, owner and activation of this dependency; identify the pages and user journeys that consume it.
  • Validate controls at each hop. Remove obsolete trust, pin or isolate retained resources where appropriate, and plan how to disable the integration.
  • Ask the supplier about downstream dependencies and change notification; monitor approved content and infrastructure changes.

Read the trust-map guide →

Source citations · 1 recorded relationships

Each URL relationship has a collected source reference. Order counts external domain boundaries along this path, not navigation hops. Runtime activation remains separate.

  1. Source
    https://northline.example/
    References
    https://support-service.example/widget
    Kind
    frame
    Evidence record
    2ca7b224f3e96751c9b2fac6
    Location
    iframe[src] · line 1
    Observation
    Simulated resource response. Execution and real visitor activity are not established.
    Policy assessment
    no_policy
    Integrity metadata
    No recognised pin recorded
    Sandbox
    allow-scripts
    Relationship attribution
    Collected source relationship
Full recorded chain
  1. https://northline.example/
  2. https://support-service.example/widget

First order / Selected resource

tag-service.example

https://tag-service.example/loader.js

What is

Recorded use
Resource response recorded
Registration
tag-service.example: No registration exposure observed (UNAVAILABLE)
Impact if control changes
info
Collected at
2026-09-11 09:00:00 UTC

Simulated resource response. Execution and real visitor activity are not established.

Activation, visibility & dated checks
Activation
The document loads this script or application control flow reaches the import.
Tracking / visibility
If a request reaches the endpoint, its operator can see request metadata such as path, query and timing. Client address, referrer and credentials depend on the client, policy and intermediaries. The anonymous scan does not establish exposure of real users or their data.
Registration checked
2026-09-11 09:00:00 UTC
Check valid until
2026-09-11 10:00:00 UTC
Path basis
Each URL relationship has a collected source reference. Order counts external domain boundaries along this path, not navigation hops. Runtime activation remains separate.

What if

Assumed breach. Assume an attacker can replace the selected external resource's response with malicious content. Independent application configuration and controls remain as observed.

Replacement code can read or change the page and its event handlers if it is accepted and executed. CSP, integrity checks, execution context and browser controls determine whether that path works.

Assess the consuming page and resource context on this path. A collected dependency chain is not proof every stage executes or that the whole organisation is affected.

Conditions and controls (6)
  • Any effective integrity check must still be satisfied.
  • Assumed breach is a scenario, not evidence of compromise. Registration availability does not establish or exclude supplier compromise.
  • No applicable enforced CSP was collected; other loading and origin controls still apply.
  • Recognised integrity metadata is present. Where effective, replacement bytes must match a permitted digest; enforcement has not been independently demonstrated.
  • Recognised integrity metadata protects the bytes at https://tag-service.example/loader.js if enforced. It does not pin that resource's separately fetched dependencies.
  • The affected application path must remain reachable and use this reference.

Decisions to make

  • Confirm the purpose, owner and activation of this dependency; identify the pages and user journeys that consume it.
  • Validate controls at each hop. Remove obsolete trust, pin or isolate retained resources where appropriate, and plan how to disable the integration.
  • Ask the supplier about downstream dependencies and change notification; monitor approved content and infrastructure changes.

Read the trust-map guide →

Source citations · 2 recorded relationships

Each URL relationship has a collected source reference. Order counts external domain boundaries along this path, not navigation hops. Runtime activation remains separate.

  1. Source
    https://northline.example/
    References
    https://northline.example/app.js
    Kind
    script
    Evidence record
    reference-1
    Location
    script[src] · line 1
    Observation
    Simulated resource response. Execution and real visitor activity are not established.
    Policy assessment
    no_policy
    Integrity metadata
    No recognised pin recorded
    Sandbox
    Not recorded
    Relationship attribution
    Collected source relationship
  2. Source
    https://northline.example/app.js
    References
    https://tag-service.example/loader.js
    Kind
    script
    Evidence record
    4eecd9cbb9fa2a545dc8cc7f
    Location
    script[src] · line 1
    Observation
    Simulated resource response. Execution and real visitor activity are not established.
    Policy assessment
    no_policy
    Integrity metadata
    Recognised · enforcement still matters
    Sandbox
    Not recorded
    Relationship attribution
    Collected source relationship
Full recorded chain
  1. https://northline.example/
  2. https://northline.example/app.js
  3. https://tag-service.example/loader.js

Second order / Selected resource

frame-assets.example

https://frame-assets.example/widget.js

What is

Recorded use
Resource response recorded
Registration
frame-assets.example: No registration exposure observed (UNAVAILABLE)
Impact if control changes
high
Collected at
2026-09-11 09:00:00 UTC

Simulated resource response. Execution and real visitor activity are not established.

Activation, visibility & dated checks
Activation
The document loads this script or application control flow reaches the import.
Tracking / visibility
If a request reaches the endpoint, its operator can see request metadata such as path, query and timing. Client address, referrer and credentials depend on the client, policy and intermediaries. The anonymous scan does not establish exposure of real users or their data.
Registration checked
2026-09-11 09:00:00 UTC
Check valid until
2026-09-11 10:00:00 UTC
Path basis
Each URL relationship has a collected source reference. Order counts external domain boundaries along this path, not navigation hops. Runtime activation remains separate.

What if

Assumed breach. Assume an attacker can replace the selected external resource's response with malicious content. Independent application configuration and controls remain as observed.

Replacement code could read or change the embedded document and its event handlers if accepted and executed there. This does not establish access to the parent document.

This path crosses an embedded-document boundary. Code or content normally affects that document; impact on the parent needs additional origin, sandbox or messaging conditions.

Conditions and controls (4)
  • Assumed breach is a scenario, not evidence of compromise. Registration availability does not establish or exclude supplier compromise.
  • Embedded-document sandbox on https://support-service.example/widget: allow-scripts. Retain and validate the applicable restrictions.
  • No applicable enforced CSP was collected; other loading and origin controls still apply.
  • The affected application path must remain reachable and use this reference.

Decisions to make

  • Confirm the purpose, owner and activation of this dependency; identify the pages and user journeys that consume it.
  • Validate controls at each hop. Remove obsolete trust, pin or isolate retained resources where appropriate, and plan how to disable the integration.
  • Ask the supplier about downstream dependencies and change notification; monitor approved content and infrastructure changes.

Read the trust-map guide →

Source citations · 2 recorded relationships

Each URL relationship has a collected source reference. Order counts external domain boundaries along this path, not navigation hops. Runtime activation remains separate.

  1. Source
    https://northline.example/
    References
    https://support-service.example/widget
    Kind
    frame
    Evidence record
    reference-4
    Location
    iframe[src] · line 1
    Observation
    Simulated resource response. Execution and real visitor activity are not established.
    Policy assessment
    no_policy
    Integrity metadata
    No recognised pin recorded
    Sandbox
    allow-scripts
    Relationship attribution
    Collected source relationship
  2. Source
    https://support-service.example/widget
    References
    https://frame-assets.example/widget.js
    Kind
    script
    Evidence record
    bcadaa990d737152faf7b15a
    Location
    script[src] · line 1
    Observation
    Simulated resource response. Execution and real visitor activity are not established.
    Policy assessment
    no_policy
    Integrity metadata
    No recognised pin recorded
    Sandbox
    Not recorded
    Relationship attribution
    Collected source relationship
Full recorded chain
  1. https://northline.example/
  2. https://support-service.example/widget
  3. https://frame-assets.example/widget.js

Second order / Selected resource

telemetry-service.example

https://telemetry-service.example/events

What is

Recorded use
Resource response recorded
Registration
telemetry-service.example: No registration exposure observed (UNAVAILABLE)
Impact if control changes
medium
Collected at
2026-09-11 09:00:00 UTC

Simulated resource response. Execution and real visitor activity are not established.

Activation, visibility & dated checks
Activation
Application control flow reaches the request. Unvisited states and user-triggered paths are not exercised.
Tracking / visibility
If a request reaches the endpoint, its operator can see request metadata such as path, query and timing. Client address, referrer and credentials depend on the client, policy and intermediaries. The anonymous scan does not establish exposure of real users or their data.
Registration checked
2026-09-11 09:00:00 UTC
Check valid until
2026-09-11 10:00:00 UTC
Path basis
Each URL relationship has a collected source reference. Order counts external domain boundaries along this path, not navigation hops. Runtime activation remains separate.

What if

Assumed breach. Assume an attacker can replace the selected external resource's response with malicious content. Independent application configuration and controls remain as observed.

Returned data can influence content, decisions or page events where the application consumes it. Code execution requires additional unsafe handling; a request alone does not establish it.

Assess the consuming page and resource context on this path. A collected dependency chain is not proof every stage executes or that the whole organisation is affected.

Conditions and controls (4)
  • Assumed breach is a scenario, not evidence of compromise. Registration availability does not establish or exclude supplier compromise.
  • No applicable enforced CSP was collected; other loading and origin controls still apply.
  • Recognised integrity metadata protects the bytes at https://tag-service.example/loader.js if enforced. It does not pin that resource's separately fetched dependencies.
  • The affected application path must remain reachable and use this reference.

Decisions to make

  • Confirm the purpose, owner and activation of this dependency; identify the pages and user journeys that consume it.
  • Validate controls at each hop. Remove obsolete trust, pin or isolate retained resources where appropriate, and plan how to disable the integration.
  • Ask the supplier about downstream dependencies and change notification; monitor approved content and infrastructure changes.

Read the trust-map guide →

Source citations · 3 recorded relationships

Each URL relationship has a collected source reference. Order counts external domain boundaries along this path, not navigation hops. Runtime activation remains separate.

  1. Source
    https://northline.example/
    References
    https://northline.example/app.js
    Kind
    script
    Evidence record
    reference-1
    Location
    script[src] · line 1
    Observation
    Simulated resource response. Execution and real visitor activity are not established.
    Policy assessment
    no_policy
    Integrity metadata
    No recognised pin recorded
    Sandbox
    Not recorded
    Relationship attribution
    Collected source relationship
  2. Source
    https://northline.example/app.js
    References
    https://tag-service.example/loader.js
    Kind
    script
    Evidence record
    reference-2
    Location
    script[src] · line 1
    Observation
    Simulated resource response. Execution and real visitor activity are not established.
    Policy assessment
    no_policy
    Integrity metadata
    Recognised · enforcement still matters
    Sandbox
    Not recorded
    Relationship attribution
    Collected source relationship
  3. Source
    https://tag-service.example/loader.js
    References
    https://telemetry-service.example/events
    Kind
    connect
    Evidence record
    c760360ee01510b4d4622bca
    Location
    JavaScript fetch · line 1
    Observation
    Simulated resource response. Execution and real visitor activity are not established.
    Policy assessment
    no_policy
    Integrity metadata
    No recognised pin recorded
    Sandbox
    Not recorded
    Relationship attribution
    Collected source relationship
Full recorded chain
  1. https://northline.example/
  2. https://northline.example/app.js
  3. https://tag-service.example/loader.js
  4. https://telemetry-service.example/events

Select a domain or connection to inspect its resource path. Switch between What is and What if. Supporting controls and citations open on request.