跳转到安全报告
⚠️
该域名已被标记为恶意域名
安全引擎报告检测:18。 请格外小心——不要输入凭据或个人信息。
域安全和威胁情报

bafkreia2pngndebebyscsmxex5zjszaf5sdg3xso2ugg63rrsv3qqgwumu[.]ipfs[.]dweb[.]link

“IPFS Service Worker Gateway | HEAD@0a11d6b”

威胁判定 关键 95/100 证据评分
可用性 未验证 当前可达性未经验证
病毒检测总数:18/91
2026年7月26日 CDN
报告概览

bafkreia2pngndebebyscsmxex5zjszaf5sdg3xso2ugg63rrsv3qqgwumu.ipfs.dweb.link — 未验证. 证据摘要: VirusTotal 18/91 (alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET); PhishDestroy score 95/100. 注册商: CSC.

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

证据摘要
重要
Ref
D11F434D
评分
95/100

The domain bafkreia2pngndebebyscsmxex5zjszaf5sdg3xso2ugg63rrsv3qqgwumu.ipfs.dweb.link was created on February 24, 2017 and is currently registered through CSC Corporate Domains, Inc. DNS resolution points to the single IPv4 address 209.94.90.3, and the authoritative name servers are clarissa.ns.cloudflare.com and tate.ns.cloudflare.com, indicating use of Cloudflare’s DNS infrastructure. VirusTotal reports that 18 of 91 security vendors have flagged the domain, confirming that a notable portion of the security community considers it malicious. The domain is actively listed on two public blocklists and is specifically blocked by PhishDestroy and OpenPhish, reinforcing its classification as a high‑risk phishing infrastructure.

Its status remains active as of the report date, July 26, 2026, and no evidence of takedown or remediation has been observed. Defenders should treat any traffic to this host as hostile. Immediate mitigation steps include adding the domain and its resolving IP (209.94.90.3) to network deny lists, updating DNS sinkhole configurations, and ensuring endpoint protection solutions ingest the latest blocklist entries from PhishDestroy and OpenPhish.

Continuous monitoring of Cloudflare name‑server activity may reveal additional sub‑domains or related infrastructure. Because the public evidence does not include details such as SSL certificates, HTTP response codes, or page content, analysts should consider active probing in a controlled environment to gather further indicators while maintaining isolation. Until more granular indicators are uncovered, the recommended baseline response is to block the domain at perimeter and endpoint layers, alert SOC staff of its high‑risk status, and correlate any internal logs that reference the IP or domain with existing detection rules.

VirusTotal
VirusTotal
18 det.
URLScan
URLScan
ScamAdviser
Scamadviser
80/100
TLS 证书
Let's Encrypt
年龄
9.5 yr
观测状态
未验证
PhishDestroy
DestroyList
已列入
数据覆盖范围 VirusTotal 18 / 91 URLQuery 未检查 PhishStats 未检查 OTX no community references CF雷达 scan completed URLScan capture 存储的报告 URLScan verdict 分析完成 DNS 阻断 未检查 TLS valid certificate, 84d WHOIS 116 mo old 屏幕截图 2 captures · 2 sources 重定向链 未探查 Scamadviser 80/100

威胁响应 Pipeline

发现
Checks
Reports
可用性
10/12

公共封禁名单状态

已保存的截图

域名情报

域名
URLScan Verdict 分析完成 score 0 report ↗
服务器 / ASN cloudflare · AS40680 Protocol Labs
IP Context Cloudflare shared edge origin IP hidden Edge-IP 声誉不属于此域。
平台提供商 CSC US(US)
滥用举报联系方式abuse@ipfs.io, tldsupport@cscinfo.com
IP 地址 209.94.90.3 CDN
地理位置US San Francisco, US
网络AS40680 · Protocol Labs
源 IP 隐藏在 CDN 代理后面。边缘地址的反向 IP 结果包含不相关的租户;查找源头需要被动 DNS 或证书透明数据。
技术细节DNS、SSL SAN、时间戳
首次发现2026年7月26日
DOM Analysisanalyzed 2026年7月26日score 88/100
IoC Extractionscanned 2026年7月29日0 wallet · 0 Telegram IoCs
Submitted URLhttp://bafkreia2pngndebebyscsmxex5zjszaf5sdg3xso2ugg63rrsv3qqgwumu.ipfs.dweb.link/
域名服务器clarissa.ns.cloudflare.comtate.ns.cloudflare.com
TLS Fingerprint
TLS Observationvalid from 2026年7月21日scanned 2026年7月26日
TLS SAN Domainsdweb.link
Favicon Hash
页面标题
IPFS Service Worker Gateway | HEAD@0a11d6b
TLS 证书
Valid transport encryption · 颁发者 Let's Encrypt · valid for 84 days
所用技术 · 3 identified
IPFS
Network storage

IPFS is a peer-to-peer hypermedia protocol that provides a distributed hypermedia web.

ipfs.tech 置信度 100%
Cloudflare
CDN

Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.

www.cloudflare.com 置信度 100%
HTTP/3
Miscellaneous

HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.

httpwg.org 置信度 100%
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据,帮助保护他人

VirusTotal 分析

18 / 91 安全供应商标记了该域
View on VT
Last analyzed Previous stored snapshot: 18 detections
alphaMountain.ai
BitDefender
CRDF
CyRadar
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
LevelBlue
Lionic
Netcraft
OpenPhish
Sophos
VIPRE
Webroot

存档证据

Wayback Machine Snapshot
历史快照可供证据审查
View Archive
网站性能分析

Google PageSpeed Insights — mobile performance audit of bafkreia2pngndebebyscsmxex5zjszaf5sdg3xso2ugg63rrsv3qqgwumu.ipfs.dweb.link · checked Jul 26, 2026

93
Good
Performance
FCP
2.56s
First Contentful Paint
LCP
2.56s
Largest Contentful Paint
CLS
0.006
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.56s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor

证据与外部报告

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

If credentials were compromised, report immediately. Do not engage with recovery scammers.

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

欧洲刑警组织
查找您所在欧盟国家/地区的官方报告渠道
National police directory
警惕“数据恢复”诈骗! 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

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

97个国家目录
AI辅助草稿——事件详细信息由AI提供商处理 自行审核并提交

检查任意域名

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

立即扫描

举报网络钓鱼

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

报告

实时威胁动态

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

监控

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

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

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

嵌入此报告

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

embed.html
<iframe
  src="https://phishdestroy.io/zh/embed/domain/bafkreia2pngndebebyscsmxex5zjszaf5sdg3xso2ugg63rrsv3qqgwumu.ipfs.dweb.link"
  title="PhishDestroy threat report for bafkreia2pngndebebyscsmxex5zjszaf5sdg3xso2ugg63rrsv3qqgwumu.ipfs.dweb.link"
  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>