VirusTotal
17 / 89
“Suspected Phishing | Cloudflare”
ledgrr--live.pages.dev — 可达 · 访问受限 (HTTP 403). 品牌冒充:Ledger; 诈骗类型:Impersonation. 证据摘要: VirusTotal 17/89 (Criminal IP, alphaMountain.ai, BitDefender, CyRadar, ESET); URLScan malicious verdict; 2 external blocklist matches (MetaMask, SEAL); CF Radar malicious; PhishDestroy score 100/100. 注册商: Cloudflare Pages.
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
As of 2026-10-01, ledgrr--live.pages.dev returned HTTP status 403, a dated response recorded during the HTTP check. The same record set shows an internal listing by PhishDestroy, noted separately from external blocklist results.
On 2026-09-08, ledgrr--live.pages.dev was first observed according to the recorded timeline. The HTTP check dated 2026-10-01 recorded status 403, while the PageSpeed check dated 2026-09-16 recorded a performance score of 99. The SSL scan dated 2026-09-16 named Google Trust Services / WE1 as issuer. VirusTotal, checked 2026-09-18, recorded 17 detections across 89 scanners. The external blocklist check dated 2026-10-01 named MetaMask and SEAL, with a count of 2.
The PhishDestroy internal listing and the MetaMask and SEAL external listings come from different checks, so their dates should be compared rather than merged. The HTTP 403 response and the PageSpeed score of 99 were recorded on different dates, which limits direct comparison of those observations. Because the VirusTotal check and the blocklist check occurred on separate dates, changes between them cannot be established from this record set alone.
Retain the dated records for ledgrr--live.pages.dev, including the PhishDestroy listing, the MetaMask and SEAL entries, and the VirusTotal result, so later checks can be compared against them. When reviewing ledgrr--live.pages.dev again, record the date and outcome of each check separately rather than treating older observations as current. Avoid submitting sensitive information while reviewing ledgrr--live.pages.dev, since the recorded HTTP 403 response does not establish how the domain behaves now.
针对该主机的爬虫与浏览器观察记录,以及针对“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.
4f7292a8ddf7130939cd9e0a3c7f3d35d6d45e3ac1016fece4c796312d341714Saved 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 ledgrr--live.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