Why this matters — ICANN RAA §3.18 obligation & victim-assistance
On PhishDestroy delivered an evidence-backed abuse report
(repeated 2 times, most recently ) to domainabuse@service.aliyun.com with the evidence stored for the case at that time.
More than 5 months later, the phishing infrastructure remains reachable
.
Under ICANN RAA §3.18 accredited registrars are contractually obliged to “take reasonable and prompt steps to investigate and respond appropriately to any reports of abuse.” Silence beyond 24 hours after a documented notification with verifiable evidence is not a timing issue — it is a policy decision to let the operation continue. PhishDestroy\'s position: where a registrar fails to act on clear evidence, the registrar has aligned itself with the operator of the scheme and bears co-responsibility for downstream harm caused to victims from the moment of notification onward.
Victim-assistance obligation. If Alibaba Cloud Computing (Beijing) Co., Ltd. doesn't consider the listed detections enough proof — that is interesting in itself, given the volume of independent vendor confirmations. But after 2 separate notifications over 5 months, with the operation still active, the registrar took no measurable action to mitigate the harm caused by their client. The reasonable next step is direct help to any identified victims — contact & payment-trail disclosure, abuse-thread transcripts, registrant data preservation — since the registrar chose, by inaction, to extend the window of damage.
icefish[.]cc
icefish.cc 网络钓鱼与安全检查
“登录”
icefish.cc:VirusTotal 的 94 个引擎中有 3 个检出。查看 DNS、SSL、注册商、阻止列表和威胁情报。
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
PhishDestroy first recorded icefish.cc on Mar 5, 2026. This English evidence brief is rebuilt from the current structured observations stored for the report. The current evidence score, computed from those stored observations, is 74/100.
The latest stored availability state is “Last known active” on Aug 2, 2026 at 10:29 UTC. No conclusive HTTP response is stored, so current availability remains unverified.
VirusTotal returned 3 detections from 94 scanners in the stored check on Jul 10, 2026 at 14:58 UTC. The independent blocklist snapshot recorded 0 matches across 10 configured external sources on Aug 2, 2026 at 10:20 UTC. PhishDestroy's own listing is excluded from that count. A zero-match snapshot is not a safety verdict.
Other stored evidence. Google Safe Browsing stored no positive flag on Mar 5, 2026 at 03:51 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 0 pulse references on Mar 5, 2026 at 03:51 UTC. OTX pulses are community-intelligence references, not vendor verdicts. The Spamhaus DBL snapshot stored no positive result on Jul 14, 2026 at 02:33 UTC. That result is not evidence of safety. A URLScan capture is stored from Mar 24, 2026 at 11:56 UTC.
Stored context lists registrar Alibaba Cloud Computing (Beijing) Co., Ltd., IP address 47.105.125.215, registration date Mar 5, 2026. Except for the registration date, these fields do not share a source timestamp in this report and may change.
Treat these as stored, time-bound observations rather than a live safety guarantee. Source verdicts and reachability can change, and zero or missing vendor matches never prove that a domain is safe. Avoid interacting with the domain while uncertainty remains, and use the appeal process if this report is inaccurate.
威胁响应 Pipeline
公共封禁名单状态
滥用举报历史 · 2 stored reports over 2 days · click to expand
-
Report #1 Mar 5, 2026 · 01:51 UTCPhishing Abuse Report: icefish[.]ccdomainabuse@service.aliyun.com
-
Report #2 ICANN CC 32h still active Mar 6, 2026 · 10:47 UTCESCALATION #2 (32h active): Phishing - icefish[.]ccdomainabuse@service.aliyun.com abuse@verisign-grs.com compliance@icann.org
VirusTotal 分析
存档证据
网站性能分析
Google PageSpeed Insights — mobile performance audit of icefish.cc · checked Mar 5, 2026
证据与外部报告
您是否受到本网站的影响?
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。