Skip to main content
Sandfish

Analysis

https://santander-6b1f-vyoka-data.neuraltrust.ai/

Group7833c86c-9088-42fa-980a-aabc0afb238asubmitted urlMember 1

Results

Rules engine

AI review

AI case description

The Santander-named subdomain on neuraltrust.ai returned HTTP 401 with an “API key required” error. No page content, credential fields, or network activity indicating impersonation or data collection was observed.

Findings

2 signalsHighest severityLow

Analyzed page

Language
Detecting...

Infrastructure

Domain registration
neuraltrust.aiMore than 90 days oldRegistered 2024-02-27 · Registrar Cloudflare, Inc
Hosting
Loading...

Capture activity

Interaction
0 actions · 0 submissions · stopped: no fillable controls · download stage: no payload control
Kit source work

Loading related source work…

Discover or upload kit source

Analysis metadata

How and when the analysis ran.

Processing status
Evidence coverage
Input kind
url
Execution kind
capture
Duration
10.0s
Navigation
2 navigations
Engine version
0.4.2
Created
2026-11-20 03:14:31Z
Started
2026-11-20 03:14:31Z
Finished
2026-11-20 03:14:41Z
Archive
12.5 KB
Analysis ID
958e20aa-f6d1...
navigation incomplete: Error: Page.goto: NS_BINDING_ABORTED Call log: - navigating to "http://santander-6b1f-vyoka-data.neuraltrust.ai/", waiting until "domcontentloaded"

Document-source diagnostics

These records identify rejected document reads. A current epoch does not prove that a replacement read succeeded. Later success does not erase an earlier evidence limit.

Inspect 1 rejected read

An epoch identifies a document generation. Superseded means the document changed. Internal means a browser-owned document. Unavailable means the source identity could not be read.

Ordinals are zero-based. Unknown navigation indexes remain unknown. Scroll the table horizontally to inspect all columns.

OrdinalSource epochCurrent epochMilestoneArtifactStateObserved at (UTC)
0Unknown epochUnknown epochdom_readymilestoneunavailable
Showing 0–0 of 0
Browser-observed navigation status

The browser status can differ from the normalized origin response, including during a proxy failure. Inspect the recorded document request for origin response evidence.

NavigationBrowser-observed HTTP statusRecorded requests
0301Inspect navigation 0 requests
1401Inspect navigation 1 requests
Showing 0–0 of 0

Signals by severity

Detected findings grouped by risk

Request activity

Network requests grouped by resource type

Behavior

Recorded actions grouped by type

Network contacts

Requests to the most active hosts

Request ownership

First-party and third-party requests

Response MIME types

Network responses grouped by MIME type