Security engines reporting a detection: 12. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
On 2026-10-01, ledger-livv.pages.dev returned an HTTP 403 response, a dated source observation recorded during an HTTP check. Separately, the domain appeared on two named external blocklists, MetaMask and SEAL, and carried a phishdestroy internal listing.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 403 for ledger-livv.pages.dev. A blocklist check on 2026-10-01 found the domain on two external blocklists, MetaMask and SEAL. PhishDestroy's internal listing was recorded as true. VirusTotal, checked on 2026-09-11, reported 12 detections across 89 scanners. The domain was first observed on 2026-08-31, and its IP address resolved to Cloudflare, Inc. in CA.
Interpretation
The named source records describe distinct measurements rather than a single unified finding. The blocklist entries and the internal listing reflect separate listing decisions, while the VirusTotal figures come from a different scanning context. The first-observed date precedes the HTTP and blocklist checks, so the records span more than one point in time. Because the source dates differ, the observations should be read as separate snapshots, not as a combined trend.
Recommended Actions
Preserve the HTTP check record for ledger-livv.pages.dev and the blocklist check record as separate artifacts for later comparison. Compare the MetaMask and SEAL listings against the phishdestroy internal listing in separate reviews. Retain the VirusTotal scan record alongside the first-observed entry so later checks can be compared against them. Re-check the domain's HTTP response and blocklist status periodically, and document each result with its own date.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
IP ContextCloudflare shared edgeorigin IP hiddenEdge-IP reputation is not attributed to this domain.
Platform providerCloudflare Pages
HTTP Status403 Forbidden
Elapsed Since First Report10 days
What we count
Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Reachable · access restricted.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 31, 2026
Page Title
Suspected Phishing | Cloudflare
Impersonates
Ledger
TLS Certificate
Hostname coverage not recorded·
Issued by WE1
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
172.66.47.9
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
TLS certificate
Issuer
WE1
Hostname coverage
Hostname coverage not recorded
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Observed timelinelast reachable: 2026-08-31 20:28:19 UTCcurrent episode first observed: 2026-10-01 01:37:13 UTCobserved RIP window: 2026-08-31 20:28:19 UTC → 2026-10-01 01:37:13 UTC · 725.15hmidpoint estimate ≈ 2026-09-15 23:02:46 UTC · precision very low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 3 identified
H
HSTS
Security
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Last analyzed First positive detection Previous stored snapshot: 12 detections
alphaMountain.ai
BitDefender
ESET
Fortinet
G-Data
Gridinsoft
LevelBlue
Lionic
OpenPhish
Sophos
VIPRE
Webroot
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-09-10 22:00:33 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-10 21:43:11 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
ledger-livv.pages.dev detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
3 evidence signal groups linked0 reports recordedReachable · access restricted
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · ledger-livv.pages.dev
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
