The domain blockdagmainnet.network is identified as a phishing site involved in brand impersonation, specifically targeting the BlockDAG brand. This domain was used to deceive users into believing they were engaging with the legitimate BlockDAG network, potentially leading to financial loss or credential theft. The site has been taken offline, reducing immediate risk, but users should remain cautious of similar threats.
Technical analysis of blockdagmainnet.network reveals several indicators of malicious activity. VirusTotal reports that 2 out of 95 security vendors, including alphaMountain.ai and Bfore.Ai PreCrime, detected this domain as malicious. It was registered through HOSTINGER operations, UAB, on July 20, 2025, and resolved to the IP address 64.29.17.1, located in the US under AS16509 Amazon.com, Inc. The domain appears on four security blocklists, including PhishDestroy, Polkadot, Enkrypt, and Codeesura. The site did not have an SSL certificate, and its page title was 'Become a Part Of BlockDAG Network | Buy BDAG Coins & Miners'.
Users who interacted with blockdagmainnet.network should take immediate safety measures. If cryptocurrency wallets were connected, it is advisable to revoke token approvals and move funds to a new wallet. For those who provided credentials, changing passwords and enabling two-factor authentication is crucial. Monitoring accounts for suspicious activity is recommended. Incidents can be reported to security vendors and blocklist providers to aid in mitigating future threats.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='blockdagmainnet.network', port=80): Max retries exceeded with url: / (Caused by NewConnect
DOM Analysisanalyzed 2026年4月23日score 10/1001 brand signal
Submitted URLhttps://blockdagmainnet.network/
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.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:09:17 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-06-16 16:39:01 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-16 16:39:01 UTC → 2026-09-30 16:14:55 UTC · 2,543.60hmidpoint estimate ≈ 2026-08-08 16:26:58 UTC · precision very low · basis bounded
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.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
(LT)
