On 2026-10-03, worldlibertyfinance.pages.dev returned an HTTP 403 status code, showing that access to the site was restricted on that date. The domain also achieved a high PageSpeed performance score earlier, indicating efficient technical performance as of 2026-09-02.
Recorded Evidence
MetaMask and SEAL both listed worldlibertyfinance.pages.dev on their external blocklists as of 2026-10-03. Google Safe Browsing flagged the domain for social engineering on 2026-09-04. VirusTotal reported 9 detections out of 90 scanners on 2026-09-04. Phishdestroy internally listed the domain by 2026-10-03.
Interpretation
The recorded evidence shows that worldlibertyfinance.pages.dev was identified by multiple independent security sources over several weeks. The combination of external blocklist entries, a Google Safe Browsing flag, and VirusTotal detections highlights that the domain drew attention from both public and internal monitoring systems. The HTTP 403 status code means that direct access was restricted during the most recent check, which may limit further review of its content.
Recommended Actions
For worldlibertyfinance.pages.dev, retain records from MetaMask, SEAL, Google Safe Browsing, VirusTotal, and Phishdestroy for future reference. Compare these sources to monitor any changes in blocklist or detection status. Note the HTTP 403 response as a factor that could affect subsequent attempts to access or analyze the site.
Extracted from stored page analysis
Observed indicators
0 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
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-26 10:28:20 UTCcurrent episode first observed: 2026-10-01 01:35:40 UTCobserved RIP window: 2026-08-26 10:28:20 UTC → 2026-10-01 01:35:40 UTC · 855.12hmidpoint estimate ≈ 2026-09-13 06:02:00 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.
技术 · 3 identified
H
HSTS
安全
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: 9 detections
ADMINUSLabs
ChainPatrol
alphaMountain.ai
BitDefender
ESET
Fortinet
卡巴斯基
Lionic
Sophos
网站性能分析
Google PageSpeed Insights — mobile performance audit of worldlibertyfinance.pages.dev· checked Sep 2, 2026
99
Good
Performance
FCP
0.77s
First Contentful Paint
LCP
1.83s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2s
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-02 22:00:23 UTC
Domain state transitioned from alive to dead.
Status Check2026-09-02 18:49:18 UTC
Telemetry event observed.
Threat First Observed2026-09-02 18:33:09 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
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.
(US)
