Skip to main content
Sandfish

Search - Microsoft Bing

https://www.bing.com/

Group9084687b-a0d9-4b3d-bbbc-c8f151cc1e6csubmitted urlMember 1

Results

Rules engine

AI review

AI case description

The target briefly displayed a browser-check screen, then navigated to the legitimate Bing homepage; no credential controls or submissions were observed. The evidence does not establish why the redirect occurred or show abuse.

Findings

1 signalHighest severityInformational

Analyzed page

Language
Detecting...

Infrastructure

Domain registration
w1-whatsapp.com.cnunsupported
Hosting
Loading...

Capture activity

Interaction
1 action · 0 submissions · stopped: no fillable controls · download stage: no payload control
  1. 1. clicksucceededAccept
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
23.0s
Navigation
2 navigations
Engine version
0.4.2
Created
2026-11-21 19:09:01Z
Started
2026-11-21 19:09:01Z
Finished
2026-11-21 19:09:24Z
Archive
1.0 MB
Favicon source
html_link / favicon-v7
Analysis ID
c58dbd0a-6a86...
navigation incomplete: document evidence source unavailable

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 1Navigation 0document_readyscreenshotunavailable
1Generation 1Navigation 0Generation 1Navigation 0dom_readyscreenshotunavailable
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
1200Inspect 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