The domain vestingblockdag.network is identified as a brand impersonation threat targeting BlockDAG, a cryptocurrency network. Analysis confirms the domain was designed to mimic legitimate BlockDAG investment and mining opportunities, with the page title explicitly stating 'Become a Part Of BlockDAG Network | Buy BDAG Coins & Miners.' The domain is currently offline, though its prior activity raises concerns regarding fraudulent financial solicitations. Infrastructure analysis reveals the domain was registered on February 25, 2026, through HOSTINGER operations, UAB. It resolves to the IP address 145.223.104.2 and has been flagged by 2 of 95 security vendors on VirusTotal. The domain appears on three security blocklists and has been actively blocked by multiple threat intelligence platforms. Detection rates, though modest, align with emerging phishing campaigns targeting cryptocurrency investors. The domain is no longer accessible, but its prior deployment and infrastructure warrant continued monitoring. Organizations and individuals are advised to verify investment portals through official BlockDAG channels and treat unsolicited cryptocurrency offers with heightened scrutiny. Blocklist integration and endpoint protection updates are recommended to mitigate residual risks from similar impersonation attempts.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='vestingblockdag.network', port=80): Max retries exceeded with url: / (Caused by NewConnect
DOM Analysisanalyzed 2026年7月29日score 56/1001 brand signal
Submitted URLhttp://vestingblockdag.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.
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:11:42 UTC
RDAP registration未知
Observed timelinecurrent episode first observed: 2026-09-30 16:14:55 UTCfirst terminal observation: 2026-09-30 16:14:55 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.
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.
VirusTotal Detections Update2026-06-26 16:30:29 UTC
VirusTotal scanner detections updated from 4 to 2. Added scanner alerts: Gridinsoft, alphaMountain.ai. Resolved alerts: ADMINUSLabs, G-Data, SOCRadar, Sophos.
16 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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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)
