VirusTotal
12 / 89
“Suspected Phishing | Cloudflare”
liv-ledger.pages.dev — 可达 · 访问受限 (HTTP 403). 品牌冒充:Ledger; 诈骗类型:Impersonation. 证据摘要: VirusTotal 12/89 (alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker, Fortinet); URLScan malicious verdict; 2 external blocklist matches (MetaMask, SEAL); CF Radar malicious; PhishDestroy score 100/100. 注册商: Cloudflare Pages.
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
liv-ledger.pages.dev returned HTTP 403 on 2026-10-01, a dated response recorded during an HTTP check. The same domain was first observed on 2026-09-08, giving a roughly three-week window between first sighting and that response.
The external blocklist count stood at 2 on 2026-10-01, listing MetaMask and SEAL. VirusTotal recorded 12 detections across 89 scanners on 2026-09-18. PhishDestroy's internal listing was true, and the SSL certificate, scanned 2026-09-16, was issued by Google Trust Services / WE1. PageSpeed on 2026-09-16 returned a performance score of 99, while the host IP 172.66.45.3 resolved to Cloudflare, Inc. in CA.
These sources observe the domain on different dates, so the blocklist count, the VirusTotal detections and the HTTP response cannot be treated as one simultaneous snapshot. The MetaMask and SEAL listings and the PhishDestroy internal listing are separate named records, and their timing relative to the 2026-09-18 VirusTotal scan is not established here. The certificate and PageSpeed observations from 2026-09-16 sit between the first sighting and the later checks, which affects how directly they can be compared.
Anyone reviewing liv-ledger.pages.dev should retain dated copies of each observation, including the 2026-10-01 HTTP result and the 2026-09-18 VirusTotal figures, so later checks can be compared against the same source. Repeat the same named checks on a consistent schedule and note each date, since the external blocklists and VirusTotal can change independently. Avoid submitting passwords, wallet credentials or other sensitive information while the review is in progress.
针对该主机的爬虫与浏览器观察记录,以及针对“Keitaro”式流量分配系统的实时指纹检测。
cloudflare扫描说明: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
扫描期间服务提供商的响应: cloudflare_phishing_interstitial
Edge-IP 声誉不属于此域。
Location describes the IP network.
da3863af24ae2e14ac2fd812d77a8e924167fe1d6d55e7d69290cb2d4df541a9Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of liv-ledger.pages.dev · checked Sep 16, 2026
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
已存储 151 个仿冒域名
显示 151 个中的 100 个
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
Template-based draft · optional AI wording assistance requires separate consent