VirusTotal
5 / 91 engine detections
打开报告“SafeguardX — Multi-Chain Crypto Wallet”
被列入黑名单的域名: safeguardx.net — 内容不可用 (HTTP 410). 证据摘要: VirusTotal 5/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar); URLQuery 2 det.…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
5 / 91 engine detections
打开报告2 det.
打开报告4 community references
打开报告provider verdict: clean
打开报告No threat flag
打开报告No malicious flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
safeguardx.net is an impersonation phishing page that presented itself as "SafeguardX — Multi-Chain Crypto Wallet". It was aimed at people looking for a wallet that holds assets across several blockchains. PhishDestroy first flagged it on 2026-09-24. The site has been offline since 2026-10-01, and its root still served no content when last checked on 2026-10-19.
Sites like this use a polished wallet brand to look like a legitimate product page. Visitors are usually pushed toward one of two traps. The first is an "import" or "restore" form that asks for a recovery phrase or private key. The second is a wallet connection that requests signatures or token approvals. Either one gives the operator control of the victim's funds, which can be emptied in minutes and cannot be recovered.
On 2026-10-01, five of 91 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That is a low count, but these are independent vendors with no link to our listing. The domain also appears in four AlienVault OTX threat pulses, so other researchers tracked it too. PhishDestroy carries it on its blocklist.
The domain was registered through Namecheap on 2026-05-01. That is almost five months before it reached our feed, so the name sat unused or ran quietly for a long time before being caught. Traffic went through Cloudflare, with the address resolving to a Canadian network location. Because Cloudflare acts as a proxy, that address belongs to Cloudflare's edge network and does not reveal the operator's real server.
If you typed a recovery phrase or private key into this site, treat that wallet as compromised. Create a new wallet on a trusted device and move any remaining assets to it right away. If you connected a wallet or signed anything, revoke every token approval granted around that time with a reputable approval checker, and watch for unexpected transfers. Never use a seed phrase on a website, whatever brand it shows. Security teams should block safeguardx.net at DNS and proxy level, keep watching it in case it comes back online, and search logs for any users who visited it between 2026-09-24 and 2026-10-01.
Edge-IP 声誉不属于此域。
rayne.ns.cloudflare.comthomas.ns.cloudflare.comaspmx.l.google.compriority 1alt2.aspmx.l.google.compriority 5alt1.aspmx.l.google.compriority 5alt3.aspmx.l.google.compriority 10alt4.aspmx.l.google.compriority 10Location describes the IP network.
60f49853acd3db27c65e74c0de9a5200794835bb4efef77b557250518ca7c7afSaved 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 safeguardx.net · checked Sep 24, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
safeguardx.net
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→inactive
http_no_content
未知→inactive
http_no_content
未知→inactive
http_no_content
未知→inactive
http_no_content
未知→inactive
http_no_content
未知→inactive
http_no_content
未知→inactive
http_no_content
未知→inactive
http_no_content
未知→inactive
http_no_content
可访问→不可用
3→4
2→3
1→2
可访问
5/91 engine detections
View sourceNo threat flag
View source4 community references
View sourcePD-20260923-EBF994
Page captured
View sourcesafeguardx.net
View sourcePD-20260923-EBF994 Recipient: abuse@namecheap.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
Template-based draft · optional AI wording assistance requires separate consent
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
safeguardx.net)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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.