Suspected Phishing | Cloudflare

https://ledgre-iolives.pages.dev/

WACZ

Groupc19f8aa5-07f0-4f76-81fb-0925cabafcf9submitted urlMember 1

Case summary

The target, observed result, and important findings.

Status
Current evaluation: Limited evidence: Access challenge, navigation error
Findings: 4Critical
Kit source work: Loading related source work…
Discover or upload kit source
Submitted URL: http://ledgre-iolives.pages.dev/ Search for this value.
Effective URL: https://ledgre-iolives.pages.dev/ Search for this value.
Domain registration: pages.devMore than 90 days oldRegistered 2020-09-02 · Registrar CloudFlare, Inc.
Language: Detecting...
Network: 14 requests across 2 hosts
Infrastructure: Loading...
Behavior: 0 recorded events
Interaction: 0 actions · 0 submissions · stopped: no fillable controls · download stage: no payload control

The summary page has no captured screenshot.

Analysis metadata

How and when the analysis ran.

Input kind: url
Execution kind: capture
Duration: 14.0s
Navigation: 2 navigations
Engine version: 0.4.1

Created: 2026-11-11 13:08:43Z
Started: 2026-11-11 13:08:43Z
Finished: 2026-11-11 13:08:57Z
Archive: 113 KB
Analysis ID: 8b5e15e5-945e...

navigation incomplete: Error: Page.goto: NS_BINDING_ABORTED Call log: - navigating to "http://ledgre-iolives.pages.dev/", 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.

Ordinal	Source epoch	Current epoch	Milestone	Artifact	State	Observed at (UTC)
0	Unknown epoch	Unknown epoch	dom_ready	milestone	unavailable	2026-11-11 13:08:48.477200 UTC

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.

Navigation	Browser-observed HTTP status	Recorded requests
0	403	Inspect navigation 0 requests
1	403	Inspect 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

Navigation

	Nav	Status	Method	Domain	Path	Type	Size

Observed cookies

Response declarations and context-wide browser observations. Navigation identifies where a jar was inspected, not which page set each cookie.

HTTP headers: complete

Browser snapshots: complete

Name	Domain	Path	Source	Attributes

Browser collection history

dom_ready · 2026-11-11T13:08:48.484365Z · navigation unknown
Collection: complete
document_ready · 2026-11-11T13:08:49.412362Z · navigation 0
Collection: complete
network_idle · 2026-11-11T13:08:49.571052Z · navigation 0
Collection: complete
pre_interaction · 2026-11-11T13:08:49.704861Z · navigation 0
Collection: complete
document_ready · 2026-11-11T13:08:50.408079Z · navigation 1
Collection: complete
final · 2026-11-11T13:08:52.195499Z · navigation 1
Collection: complete
settled · 2026-11-11T13:08:52.247220Z · navigation 1
Collection: complete