This domain is flagged as an elevated-risk brand impersonation site designed to deceive users by mimicking the Across platform. Analysis indicates the infrastructure was specifically crafted to exploit trust in the Across brand, likely for credential theft or fraudulent transaction redirection. The threat type aligns with known patterns of cryptocurrency-related phishing, though no direct crypto drainer functionality was confirmed in this instance. Infrastructure analysis reveals the domain www.zuzipay.xyz was registered on June 07, 2025, through NameCheap, Inc. and resolved to IP address 64.29.17.1. Security vendor detections on VirusTotal reached 6/95, while Gridinsoft assigned a trust score of 0/100. The domain appears on one security blocklist and was blocked by PhishDestroy. Technologies detected include Vercel hosting and HSTS implementation, with a Let's Encrypt SSL certificate providing HTTPS encryption. The page title displayed "Zuzipay," further confirming the impersonation attempt. Mitigation steps for this threat type include immediate domain blacklisting in enterprise security gateways and endpoint protection systems. Network administrators should block the IP address 64.29.17.1 and monitor for related domains registered through NameCheap with similar naming patterns. Users should be educated on verifying domain legitimacy before entering credentials, particularly for cryptocurrency platforms. Organizations should implement DMARC, DKIM, and SPF records to prevent similar brand impersonation attempts via email. Given the domain's current offline status, continuous monitoring for reactivation or migration to new infrastructure is recommended.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-1556.invalid', port=80): Max retries exceeded with url: / (Caused by Ne
DOM Analysisanalyzed 2026年3月11日score 75/1002 brand signals
Submitted URLhttps://www.zuzipay.xyz/
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of duplicate-disabled-1556.invalid· checked Jun 27, 2026
87
Needs Work
Performance
FCP
0.79s
First Contentful Paint
LCP
2.72s
Largest Contentful Paint
CLS
0.191
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.55s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Registration & observation details1
Availability observations
Last reachable observation
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
Different responses detected
content_divergence · unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-1556.invalid', port=80): Max retries exceeded with url: / (Caused by Ne
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)
