ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@key-systems.net.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
docupdate.cx is an impersonation phishing domain that trades on the Namecheap brand. Its likely targets are people who manage domains or online accounts and would trust a Namecheap-branded page. PhishDestroy first flagged it on 2026-09-16. When last checked on 2026-10-19, the site was still alive and redirecting visitors elsewhere. The page title reads "docupdate.cx is registered at Namecheap", which is the wording of a registrar parking notice, while we classify the domain as Namecheap impersonation phishing.
How the scam works
Brand-impersonation pages like this borrow the look and wording of a trusted service so a visitor lowers their guard. The name "docupdate" fits the usual pattern of a fake account notice or document update request. In this kind of scheme, the victim is steered to a login or verification form and asked for a password, a one-time code or payment details. Whoever controls the page captures that input. A stolen registrar account lets an attacker hijack domains, repoint DNS or launch further phishing from a domain the victim owns. The live redirect means the final destination can change without the domain itself changing.
Evidence
On VirusTotal, 6 of 91 engines flag the domain as of 2026-09-29: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and SOCRadar. That count is modest, but these are independent vendors reaching the same verdict. Spamhaus lists the domain in its DBL under the phishing category. MetaMask's and SEAL's blocklists carry it alongside PhishDestroy, and it appears in 4 AlienVault OTX threat pulses.
Infrastructure
The domain was registered on 2026-06-30 through CentralNic Ltd, about eleven weeks before PhishDestroy detected it. That gap suggests it was registered in advance and later put into use. It resolves to an address on Namecheap, Inc.'s network in the United States. Hosting a Namecheap lookalike on the same provider's network makes the parking-style title look more believable at a glance.
What to do
If you entered a Namecheap or other account password on this site, change it immediately, starting with your registrar and email accounts. Then reset or re-enroll two-factor authentication and review active sessions. Check your domains for unexpected transfers, contact changes or altered DNS records, and enable registrar lock if it is off. If you entered card details, contact your bank. Defenders should block docupdate.cx at DNS and proxy level, follow its redirect target, and search mail logs for messages linking to it.
DOM Analysisanalyzed 2026年9月16日score 95/1001 brand signal
Submitted URLhttp://docupdate.cx/
案件 ID
Observed page title
docupdate.cx is registered at Namecheap
Automated brand references
Namecheap
TLS 证书
颁发者 YE2
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
192.64.119.188
Network ASN
AS22612
Organization
Web-hosting.com
Observed location
Atlanta, US
Server header
nginx/1.28.3 (Ubuntu)
域名服务器 2
dns1.registrar-servers.com
dns2.registrar-servers.com
Mail routing 5 MX records
eforward2.registrar-servers.compriority 10
eforward1.registrar-servers.compriority 10
eforward3.registrar-servers.compriority 10
eforward4.registrar-servers.compriority 15
eforward5.registrar-servers.compriority 20
Location describes the IP network.
TLS 证书
Issuer
YE2
Collection time
2026-10-20 16:03:07 UTC
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-19 22:42:51 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-19 22:42:51 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
U
Ubuntu
Operating systems
Ubuntu is a free and open-source operating system on Linux for the enterprise server, desktop, cloud, and IoT.
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.
