Security engines reporting a detection: 10. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
ledger-cdn-cloud-walle-t.pages.dev returned HTTP 403 on 2026-10-01, a dated response recorded for this host. The same hostname was first observed on 2026-09-01, giving a one-month span between first sighting and that HTTP check.
Recorded Evidence
PhishDestroy listed this domain internally, and two external blocklists, MetaMask and SEAL, also carried it as of 2026-10-01. VirusTotal recorded 10 detections across 89 scanners on 2026-09-15. The SSL certificate was issued by Google Trust Services / WE1, scanned on 2026-09-13, the same date as a PageSpeed performance score of 100. The IP address 188.114.97.9 is associated with CloudFlare, Inc. in CA.
Interpretation
The blocklist, VirusTotal and SSL observations fall on different dates, so they describe separate moments rather than one synchronized snapshot. MetaMask and SEAL are named external lists, while the PhishDestroy entry is an internal listing; these are distinct sources with their own collection methods. Because the HTTP 403 and PageSpeed records were captured on different days, a reader should compare them as dated checkpoints, not as a continuous status.
Recommended Actions
Anyone reviewing ledger-cdn-cloud-walle-t.pages.dev should retain the dated records, including the 2026-10-01 HTTP response and the 2026-09-15 VirusTotal result, so later observations can be compared against them. Subsequent checks should be logged with their own dates and source names to show how the listed signals change over time. During review, avoid submitting passwords, wallet credentials or other sensitive information to the domain until the recorded signals are independently understood.
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 Report12 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 DetectedSep 1, 2026
Page Title
Suspected Phishing | Cloudflare
Impersonates
Cloudflare
TLS Certificate
Hostname coverage not recorded·
Issued by Google Trust Services / WE1· stored validity ends in 37 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
188.114.97.9
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
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-09-01 00:28:08 UTC
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: 10 detections
alphaMountain.ai
BitDefender
ESET
Fortinet
G-Data
Kaspersky
Lionic
Netcraft
Sophos
Webroot
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of ledger-cdn-cloud-walle-t.pages.dev· checked Sep 13, 2026
100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
1.82s
Largest Contentful Paint
CLS
0.001
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.76s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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-13 10:00:20 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-13 04:03: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-cdn-cloud-walle-t.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 →
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.
