Skip to main content
Sandfish

CryptoExchange

https://bitgetxdao.com/login

Groupc6720131-3618-4289-acb4-8a1588f19a78submitted urlMember 1

Results

Rules engine

AI review

AI case description

Phishing

The page at bitgetxdao.com presents a crypto-exchange login requesting email or mobile number and password, and submission reaches its own /api/auth/login endpoint, which returns 401. The evidence does not establish a connection to Bitget or show deceptive or unauthorized credential collection.

Findings

5 signalsHighest severityLow

Analyzed page

Language
Detecting...

Infrastructure

Domain registration
bitgetxdao.com8-30 days oldRegistered 2026-10-23 · Registrar NICENIC INTERNATIONAL GROUP CO., LIMITED
Hosting
Loading...

Capture activity

Interaction
3 actions · 1 submission · stopped: repeated state · download stage: no payload control
  1. 1. fillsucceededemail | | | Email address or mobile number
  2. 2. fillsucceededpassword | | | Password
  3. 3. submitsucceededNext
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
37.0s
Navigation
1 navigation
Engine version
0.4.2
Created
2026-11-20 04:14:44Z
Started
2026-11-20 04:14:45Z
Finished
2026-11-20 04:15:22Z
Archive
467 KB
Analysis ID
1bc02ae6-d5f0...
navigation incomplete: document evidence source superseded

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 2 rejected reads

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)
0Generation 1Navigation 0Generation 2Navigation 0document_readymilestonesuperseded
1Generation 1Navigation 0Generation 2Navigation 0dom_readymilestonesuperseded
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
0200Inspect navigation 0 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