跳转到安全报告
分析仪表盘
域安全和威胁情报
baap-ledger.pages.dev favicon

baap-ledger.pages.dev

“Sign in · Company Ledger”

注册商
Cloudflare Pages
Resolved IP
188.114.97.9
Registered
2026年7月2日
威胁判定 高
可用性 可达 · 访问受限 可达响应；页面内容未经验证 观察到
Source: HTTP probe
风险信号
病毒检测总数：1/89 存储的阻止列表匹配项：2 品牌冒充：Ledger 最后已知的活跃状态
2026年9月1日 Ledger CDN
API
该域名已被标记为恶意域名
安全引擎报告检测：1。 报告匹配的公共黑名单：2。 请格外小心——不要输入凭据或个人信息。
报告概览

baap-ledger.pages.dev — 可达 · 访问受限 (HTTP 403). 品牌冒充：Ledger; 诈骗类型：Credential Phishing. 证据摘要: VirusTotal 1/89 (Forcepoint ThreatSeeker); 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 66/100. 注册商: Cloudflare Pages.

为保留原始取证记录，下方的 PhishDestroy AI 详细分析仍使用英文。

VirusTotal
VirusTotal
1 det.
URLScan
URLScan
报告 ↗
TLS 证书
已过期或未验证
年龄
3 mo
观测状态
可达 · 访问受限 403
PhishDestroy
DestroyList
已列入

Source evidence

6 sources

VirusTotal

1 / 89

报告

OTX

no community references

报告

CF雷达

provider verdict: clean

报告

URLScan capture

存储的报告

报告

URLScan verdict

分析完成

报告

Google Safe Browsing

Checked; no threat flag recorded

报告

证据摘要

高
VirusTotal
1/89
URLScan
Stored capture

Assessment

On 2026-10-01, an HTTP check of baap-ledger.pages.dev returned status 403, a recorded response for that date only. The domain also appears on two external blocklists, MetaMask and SEAL, and on the internal PhishDestroy listing.

Recorded Evidence

The domain was first observed on 2026-09-01, and the HTTP check on 2026-10-01 returned status 403. VirusTotal recorded 1 detection across 89 scanners on 2026-09-13, while the external blocklist count of 2 was checked on 2026-10-01. The SSL scan on 2026-09-11 named Google Trust Services / WE1 as the issuer, and PageSpeed on 2026-09-12 returned a performance score of 88.

Interpretation

The MetaMask and SEAL listings and the internal PhishDestroy listing are separate source records, each reflecting its own collection context rather than a shared measurement. The VirusTotal detection count and the blocklist count come from different sources and dates, so they describe distinct observations rather than a combined trend. The 403 response describes only the recorded HTTP reply on its check date, not the domain's content or availability at other times.

Recommended Actions

Preserve the MetaMask and SEAL blocklist records alongside the internal PhishDestroy listing for baap-ledger.pages.dev, and keep the VirusTotal entry for later comparison. Compare the HTTP response record with the PageSpeed record in separate reviews, since they capture different aspects of the domain. Retain the SSL scan record as a distinct artifact, and re-check each source independently before drawing conclusions from the combined set.

探测与规避分析

疑似隐藏内容：扫描器显示的标题与访问者看到的标题不一致

尚未扫描 目前尚未记录到爬虫与浏览器之间的差异

针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。

存储的隐身标志
尚未扫描
上次隐形扫描
扫描器检测到的服务器头信息
cloudflare

扫描说明: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial

扫描期间服务提供商的响应: cloudflare_phishing_interstitial

显示给安检仪的标题Suspected Phishing | Cloudflare
向浏览器访问者显示的标题Sign in · Company Ledger
TDS指纹识别实时演示
七个Keitaro指纹，外加爬虫与浏览器的对比，当此面板打开时，由PhishDestroy扫描器运行。
等待

已保存的截图 · 1 capture

Primary capture 1 / 1
来源Primary capture
Recorded2026-08-31 22:16 UTC
StateStored capture
Position1 / 1
Open capture Wayback 下载

Domain details

域名
URLScan Verdict 分析完成 score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP 声誉不属于此域。
平台提供商 Cloudflare Pages US(US)
HTTP 状态码403 Forbidden
Elapsed Since First Report 12 days
统计口径 Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: 可达 · 访问受限.
每份报告包含哪些内容 存储的传出报告记录可以参考当时可用的证据，例如供应商判决、注册数据、托管详细信息、分类或屏幕截图。此页面无法推断收件人交付、接收、确认或操作的确切有效负载。
技术详情Provenance & timestamps
首次发现2026年9月1日
Favicon Hash
页面标题
Sign in · Company Ledger
Impersonates
Ledger
TLS 证书
Hostname coverage not recorded · 颁发者 Google Trust Services / WE1 · stored validity ends in 45 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 声誉不属于此域。

Location describes the IP network.

TLS 证书

Issuer
Google Trust Services / WE1
Valid from
2026-08-30 09:31:39
Valid until
2026-11-28 10:30:10
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-09-11 01:02:08 UTC
Collection source
PhishDestroy collector
Certificate fingerprint48b5b4ea43c32f1288ef28d927d301611fa8a5164adcbdbd9858117f21c24a34

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 188.114.97.9rapiddns.io

Latest Classified Outcome 2026-10-13 01:15:44 UTC

Primary outcome Provider block observed reason: Cloudflare anti-phishing block 95% confidence
Attribution Cloudflare mechanism: Phishing Interstitial source: Current Http Probe
Evidence layers Availability: Provider blocked Content: Provider blocked DNS: Stale Registration: Unknown
Latest HTTP observation Provider block observed Cloudflare anti-phishing block Cloudflare Phishing Interstitial 95% provider marker verified 2026-10-13 01:15:44 UTC
RDAP registration 未知
Observed timeline last reachable: 2026-09-13 01:16:21 UTC current episode first observed: 2026-10-01 01:39:09 UTC observed RIP window: 2026-09-13 01:16:21 UTC → 2026-10-01 01:39:09 UTC · 432.38h midpoint estimate ≈ 2026-09-22 01:27:45 UTC · precision 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
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据，帮助保护他人

VirusTotal 分析

1 / 89 安全供应商标记了该域
View on VT
Last analyzed First positive detection Previous stored snapshot: 1 detection
Forcepoint ThreatSeeker
网站性能分析

Google PageSpeed Insights — mobile performance audit of baap-ledger.pages.dev · checked Sep 12, 2026

88
Needs Work
Performance
FCP
3.05s
First Contentful Paint
LCP
3.05s
Largest Contentful Paint
CLS
0.003
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.05s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-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.
  1. Domain Status Transition 2026-09-13 10:06:03 UTC
    Domain state transitioned from alive to dead.
  2. Threat First Observed 2026-09-10 23:53:12 UTC
    Domain ingestion complete. Initial state is marked as alive.

威胁响应 Pipeline

发现
Analysis
Monitoring

10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

已捕获威胁
baap-ledger.pages.dev 已检测到并排入队，待进行全面分析
2026年9月1日
URLScan.io Capture
已存储 URLScan report with capture artifacts
Cloudflare Radar Report
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.
VirusTotal
1/89 recorded on VirusTotal
2026年9月13日
黑名单检测
见于 2 blocklists: MetaMask, SEAL
2026年10月14日
Brand Impersonation
Impersonation of Ledger
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Technical Analysis Recorded
该报告包含存储的技术或取证分析结果。
2026年10月14日
Content Observed Unavailable
监控记录了一个不可用的响应 (HTTP 403)；原因尚未独立确定。
2026年9月13日
DestroyList 已发布
Listed in the public PhishDestroy/DestroyList repository
2026年9月1日
Monitoring Continues
该域仍然可达或访问受限；未来的检查可能会更新这一观察结果。
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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web Symantec网站评审 AviraURL reporting Avast / AVGURL reporting 卡巴斯基OpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

公共封禁名单状态

仿冒域名

已存储 151 个仿冒域名

ledfger.com insertion 内部报告 ledgfer.com insertion 内部报告 ledgher.com insertion 内部报告 ledgrr.com replacement 内部报告 lefdger.com insertion 内部报告 lesdger.com insertion 内部报告 lkedger.com insertion 内部报告 lredger.com insertion 内部报告 lwedger.com insertion 内部报告 xn--ledgr-9za.com homoglyph 内部报告 ledgerk.com addition 内部报告 edger.com omission
显示全部（88）
eldger.com transposition kedger.com replacement kledger.com insertion l3dger.com replacement ldeger.com transposition ldger.com omission le.dger.com subdomain lecger.com replacement ledber.com replacement ledegr.com transposition leder.com omission ledg3r.com replacement ledge.com omission ledged.com replacement ledgedr.com insertion ledgee.com replacement ledgeer.com repetition ledgercom.com various ledget.com replacement ledgewr.com insertion ledgger.com repetition ledgir.com vowel-swap ledgor.com vowel-swap ledgr.com omission ledgre.com transposition ledgrer.com insertion ledgsr.com replacement ledgwer.com insertion ledgwr.com replacement ledher.com replacement ledhger.com insertion ledsger.com insertion ledtger.com insertion ledyer.com replacement ledzer.com replacement leedger.com insertion legder.com transposition leger.com omission lerdger.com insertion lerger.com replacement lesger.com replacement lewdger.com insertion lidger.com vowel-swap lledger.com repetition lodger.com vowel-swap lrdger.com replacement lsdger.com replacement oedger.com replacement pedger.com replacement pledger.com insertion dedger.com bitsquatting hedger.com bitsquatting iedger.com homoglyph l-edger.com hyphenation ladger.com bitsquatting lcdlger.com homoglyph lddger.com bitsquatting lebger.com homoglyph leclger.com homoglyph ledcer.com bitsquatting leddger.com insertion ledeer.com bitsquatting ledeger.com insertion ledfer.com bitsquatting ledg-er.com hyphenation ledgar.com bitsquatting ledger0.com addition ledger1.com addition ledger4.com addition ledger5.com addition ledger6.com addition ledgerb.com addition ledgerc.com addition ledgerf.com addition ledgeri.com addition ledgern.com addition ledgerq.com addition ledgerx.com addition ledges.com bitsquatting ledgez.com bitsquatting ledgur.com bitsquatting lediger.com homoglyph ledqer.com homoglyph leeger.com bitsquatting leelger.com homoglyph lefger.com bitsquatting letger.com bitsquatting ludger.com bitsquatting

显示 151 个中的 100 个

证据与外部报告

证券分析
URLScan Analyzed VirusTotal 1 det. ChainPatrol URLQuery SSL 实验室 Hostname coverage not recorded CF雷达 打开报告 WOT ScamAdviser 黑名单检查器 URLVoid Sucuri SiteCheck MDN 观测站
OSINT与情报分析
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox 哈德逊岩 Sign-in search IntelX crt.sh 证书 WHOIS Wayback
DNS 与网络
nslookup.io DNS bgp.tools ASN /路线
SEO 与域名
SpyFu Moz DA/PA Ahrefs 反向链接
深度分析
深度分析

您是否受到本网站的影响？

3 evidence signal groups linked 0 reports recorded 可达 · 访问受限
If credentials were compromised, report immediately. Do not engage with recovery scammers.

如果您输入了帐户凭据、个人或付款信息，或者从此域下载了文件，请立即采取措施。以下资源可帮助您报告事件并保护自己。

欧洲刑警组织
查找您所在欧盟国家/地区的官方报告渠道
National police directory
PhishDestroy listing review 不是执法报告
域名申诉
如果您拥有该域名并认为该列表不正确，请请求审核
警惕“数据恢复”诈骗！ 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。

97个国家目录

Template-based draft · optional AI wording assistance requires separate consent

AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交

检查任意域名

使用存储的阻止列表、WHOIS、DNS 和公共扫描证据进行威胁分析

立即扫描

举报网络钓鱼

将可疑域名提交至我们的威胁数据库——保护社区

报告

实时威胁动态

最近的网络钓鱼报告和观察到的可用性变化

监控

随时掌握最新信息，确保安全

请实时监控威胁，或者如果您认为这是误报，请对该条目提出异议

实时威胁动态 对该列表提出异议
HTML · IFRAME

嵌入此报告

在您的网站或博客上分享此威胁情报

embed.html 
<iframe
  src="https://phishdestroy.io/zh/embed/domain/baap-ledger.pages.dev"
  title="PhishDestroy threat report for baap-ledger.pages.dev"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>