Security engines reporting a detection: 3. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
On 2026-10-01, an HTTP check of liahona-ledger.pages.dev returned a 502 status code, indicating a specific server response on that date. The domain was first observed earlier, on 2026-09-08, providing a timeline for recorded activity.
Recorded Evidence
As of 2026-10-01, liahona-ledger.pages.dev appeared on the MetaMask and SEAL external blocklists. VirusTotal reported 3 detections out of 89 scanners on 2026-09-18. The domain was also listed internally by PhishDestroy, and the HTTP check on 2026-10-01 recorded a 502 response.
Interpretation
MetaMask and SEAL blocklist entries, along with the PhishDestroy internal listing, were all recorded on 2026-10-01, while the VirusTotal scan occurred on 2026-09-18. These different dates allow for comparison of how the domain was viewed by various sources over time. The 502 HTTP status and the initial observation date provide further context for evaluating changes in the domain’s status.
Recommended Actions
When reviewing liahona-ledger.pages.dev, retain all dated evidence from MetaMask, SEAL, VirusTotal, and PhishDestroy, as well as the HTTP response record. Compare any future findings with these specific records to identify changes or trends. Avoid submitting sensitive data to the domain during further review until its status is clarified.
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.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='liahona-ledger.pages.dev', port=80): Max retries exceeded with url: / (Caused by NewConnec
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
IP ContextCloudflare shared edgeorigin IP hiddenEdge-IP reputation is not attributed to this domain.
Platform providerCloudflare Pages
Time to First Unavailability8 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
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 8, 2026
Favicon Hash
Page Title
Liahona Ledger
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.44.56
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
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.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:27:44 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-08 20:28:30 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.
Last analyzed First positive detection Previous stored snapshot: 3 detections
alphaMountain.ai
Forcepoint ThreatSeeker
LevelBlue
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.
VirusTotal Detections Update2026-09-18 00:24:58 UTC
VirusTotal scanner detections updated from 2 to 3. Added scanner alerts: alphaMountain.ai.
Domain Status Transition2026-09-16 22:00:17 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-16 13:33:12 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
liahona-ledger.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 latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 17, 2026
Time to First Unavailability
195 hours elapsed from detection to the first unavailable 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 recordedContent unavailable
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 · liahona-ledger.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.
