Analysis as of July 22 2026 indicates that blockdaghelp.network is registered through Gname.com Pte. Ltd. on March 5 2026 and is currently taken offline. The domain resolves to IP 45.133.200.14, which is assigned to AS200313 (IT WEB LTD) in the Netherlands. DNS resolution shows the authoritative nameservers ns1.prohoster.name and ns2.prohoster.cc, and the MX record points to the domain itself (priority 0, host blockdaghelp.network), a configuration often observed in fraudulent mail setups. The web server presents an Nginx service behind a Cloudflare edge, and the page delivers JavaScript libraries from jsDelivr, cdnjs, and crypto‑js, all served over a Let’s Encrypt certificate issued under the R13 profile.
The page title returned by the HTTP response is “Welcome to NodeRestores”, which bears no obvious relation to the targeted brand BlockDAG, confirming the presence of brand impersonation. Gridinsoft assigns a trust score of 0 / 100, and the domain is listed on two security blocklists curated by PhishDestroy and ScamSniffer. VirusTotal analysis shows that 2 of 94 scanning engines flagged the domain, reinforcing the malicious classification. The combination of a newly created domain, low trust rating, mismatched page title, and detection by multiple independent anti‑phishing services suggests that the infrastructure was deliberately provisioned to mimic BlockDAG support channels.
At present, no additional artifacts such as phishing landing page content or credential‑harvesting scripts have been publicly disclosed, leaving the exact attack vector uncertain. Defenders should continue to block the domain at perimeter filters, monitor for any re‑hosting attempts, and advise users that any unsolicited communications referencing BlockDAG that originate from blockdaghelp.network are untrusted.
DOM Analysisanalyzed 2026年7月29日score 56/1001 brand signal
Submitted URLhttp://blockdaghelp.network/
案件 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.
(SG)
