This domain is flagged as a high‑risk generic phishing site with a crypto‑refund lure. The zone was registered on 21 Feb 2026 through Name.com, Inc. and is hosted on Amazon’s AS16509 network in Germany, resolving to 35.157.26.135. The web server presents a valid Let's Encrypt certificate (E8) and advertises Netlify and HTTP Strict Transport Security. The site appears on two public blocklists and is currently blocked by PhishDestroy and ScamSniffer; Gridinsoft assigns a trust score of 0/100. VirusTotal reports that 2 of 93 scanners have identified malicious activity. The page title “Claim Refund” aligns with the reported crypto‑scam classification. Nameservers are provided by NSOne (dns1‑dns4.p08.nsone.net). HTTP response code is 200, indicating the page is reachable. At present, no additional payload or credential‑collection details have been observed, and the exact phishing kit remains unknown. Defenders should immediately block the domain and its associated IP address, update intrusion‑detection signatures to flag Netlify‑hosted sites with HSTS that reference “coinpayments.network”, and monitor outbound traffic for connections to the AS16509 range. Continuous re‑scanning is advised to capture any future changes to the site’s content or hosting infrastructure.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-19 22:29:01 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-19 22:35:31 UTClast content: 2026-10-19 22:29:01 UTC
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.
技术 · 2 identified
N
Netlify
PaaSCDN
Platform for deploying and hosting modern web applications.
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.
(US)
