Skip to main content
Sandfish

Analysis

http://herosoftwareskills.nyc3.cdn.digitaloceanspaces.c…

Group115673eb-42a4-4b22-b2e9-9ab50158e153submitted urlMember 1

Results

Rules engine

AI review

AI case description

The DigitalOcean Spaces URL returned HTTP 403, and no page content or interactive elements were captured. The available evidence does not establish what the site was intended to do.

Findings

1 signalHighest severityLow

Analyzed page

Language
Detecting...

Infrastructure

Domain registration
digitaloceanspaces.comMore than 90 days oldRegistered 2017-02-23 · Registrar MarkMonitor Inc.
Hosting
Loading...

Capture activity

Cookies
3 observed
Interaction
0 actions · 0 submissions · stopped: error: navigation unavailable
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
12.0s
Navigation
1 navigation
Engine version
0.4.2
Created
2026-11-21 21:48:26Z
Started
2026-11-21 21:48:26Z
Finished
2026-11-21 21:48:38Z
Archive
11.0 KB
Analysis ID
ae962784-b241...
navigation incomplete: Error: Page.goto: NS_BINDING_ABORTED Call log: - navigating to "http://herosoftwareskills.nyc3.cdn.digitaloceanspaces.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 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
0403Inspect 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