Skip to main content
Sandfish

Urgent Communications

https://pr-15169-preview.urgentcomm.com/

Group1f136f20-31ac-461a-b49a-4dd38d048c53submitted urlMember 1

Case summary

The target, observed result, and important findings.

Status
Current evaluation

Limited evidence: function fingerprint limit, navigation error

Findings
4Medium
Kit source work

Loading related source work…

Discover or upload kit source
Domain registration
urgentcomm.comMore than 90 days oldRegistered 2007-08-31 · Registrar SafeNames Ltd.
Language
Detecting...
Network
122 requests across 18 hosts
Infrastructure
Loading...
Behavior
1 recorded events
Interaction
1 action · 0 submissions · stopped: no fillable controls · download stage: no payload control
  1. 1. clicksucceededEmbedded human verification control

Analysis metadata

How and when the analysis ran.

Input kind
url
Execution kind
capture
Duration
1.5m
Navigation
6 navigations
Engine version
0.4.1
Created
2026-11-11 13:00:30Z
Started
2026-11-11 13:00:31Z
Finished
2026-11-11 13:02:02Z
Archive
5.3 MB
Analysis ID
081be0e8-ec3a...
navigation incomplete: Error: Page.goto: NS_BINDING_ABORTED Call log: - navigating to "http://pr-15169-preview.urgentcomm.com/", 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 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)
0Unknown epochUnknown epochdom_readymilestoneunavailable
1Generation 2Navigation 1Generation 3Navigation 2document_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.

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