The domain coincake.exchange was registered on February 21, 2026 through Gname.com Pte. Ltd. and is currently listed as offline. Infrastructure analysis shows it resolves to the IP address 47.253.153.247, which belongs to ASN 45102, Alibaba (US) Technology Co., Ltd., located in the United States. The web server is identified as Nginx and the site enforced HTTP Strict Transport Security (HSTS).
A Let's Encrypt certificate (R13) was observed for the host, indicating HTTPS was in use before takedown. The page title retrieved before the site went offline reads "Coincake Exchange — Decentralized Perps | Multi-Chain, Liquid, Secure," suggesting a fake cryptocurrency exchange front. Security telemetry indicates the domain appears on three independent blocklists and has been actively blocked by PhishDestroy, MetaMask, and SEAL.
Google Safe Browsing flags the domain for social engineering, and VirusTotal reports 14 of 95 scanners marking the host as malicious. Although the site is no longer reachable, the combination of registrar information, hosting under a known cloud provider, the presence of a fake exchange page title, and multiple detection sources provide strong evidence that coincake.exchange was operated as a high‑risk phishing platform targeting cryptocurrency users. Defenders should continue to deny resolution to the associated IP, add the domain to URL filtering policies, and monitor for any re‑registration attempts or variations of the host name.
Extracted from stored page analysis
Observed indicators
0 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
DOM Analysisanalyzed 2026年7月27日score 83/1001 brand signal
IoC Extractionscanned 2026年7月29日0 wallet · 1 Telegram IoC
Submitted URLhttp://coincake.exchange/
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Certificate fingerprint4e0044ef65a934366b78495f4b3e5b77ff3b732c49b50962da9b516a2bed26dbCertificate names · 1 SANs
www.coincake.exchange
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-19 01:11:04 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-08-05 22:14:20 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-08-05 22:14:20 UTC → 2026-09-30 16:14:55 UTC · 1,338.01hmidpoint estimate ≈ 2026-09-02 19:14:37 UTC · precision very 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.
Recorded subdomains1
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.coincake.exchangeDomain record
The original observation time is not recorded for these hostnames.
技术 · 2 identified
N
Nginx
Web serversReverse proxies
High-performance HTTP server and reverse proxy, known for stability and low resource usage.
H
HSTS
安全
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
我应该立即采取什么措施？
紧急
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
(SG)
