The domain nexonian.digital is a confirmed phishing site engaged in brand impersonation targeting Google. It presents itself as an official Google login or service page to deceive users into entering sensitive credentials, posing an elevated risk of account compromise. No crypto drainer kit was detected. As of the latest verification, nexonian.digital has been taken offline.
Technical analysis shows nexonian.digital was flagged by 2 of 95 security vendors on VirusTotal, including Gridinsoft and SOCRadar, and appears on 3 security blocklists: PhishDestroy, MetaMask, and SEAL. The domain was registered through Global Domain Group LLC on March 02, 2026, and resolved to the IP address 95.169.191.194, hosted on AS31103 Keyweb AG in Germany. No SSL certificate was issued, and the observed page title was 'Google'. The domain used Google Cloud nameservers and was detected running Google Web Server with HSTS and HTTP/3 technologies. Gridinsoft assigned a trust score of 0 out of 100.
Users who interacted with nexonian.digital should immediately change any passwords entered on the site, especially for Google accounts, and enable two-factor authentication. Monitor accounts for unauthorized activity and report suspected fraud to Google’s support channels. Victims may also report the domain to their local cybercrime unit or platforms like Google Safe Browsing, PhishTank, or the Anti-Phishing Working Group to aid in takedown efforts.
DOM Analysisanalyzed 2026年7月29日score 63/1001 brand signal
Submitted URLhttp://nexonian.digital/
案件 ID
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.
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)
