Skip to main content
Sandfish

403 Forbidden

https://marbleonline.com/

Groupbcf4030c-ca0e-4491-afc7-9cb5485ed195submitted urlMember 1

Case summary

The target, observed result, and important findings.

Rules engine

AI review

AI case description

The site resolves to a 403 Forbidden nginx page, with no visible content, forms, or links. The evidence is incomplete and does not establish abusive activity.

Processing statusEvidence coverage

Findings

2 signalsHighest severityMedium

Analyzed page

Language
Detecting...

Infrastructure

Domain registration
marbleonline.comMore than 90 days oldRegistered 2003-09-22 · Registrar GoDaddy.com, LLC
Hosting
Loading...

Capture activity

Cookies
3 observed
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.

Input kind
url
Execution kind
capture
Duration
12.0s
Navigation
2 navigations
Engine version
0.4.2
Created
2026-11-19 03:03:45Z
Started
2026-11-19 03:03:46Z
Finished
2026-11-19 03:03:58Z
Archive
54.5 KB
Analysis ID
e9a71cf0-56e7...
navigation incomplete: Error: Page.goto: NS_BINDING_ABORTED Call log: - navigating to "http://marbleonline.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
0301Inspect navigation 0 requests
1403Inspect 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