The domain claim.vestingblockdag.network was registered on February 25 2026 through Hostinger Operations, UAB and uses the default parking nameservers ns1.dns-parking.com and ns2.dns-parking.com. DNS resolution points to IP 145.223.104.2, which belongs to AS47583 Hostinger International Limited and is geolocated in the United States. No TLS certificate is presented, indicating the site is served over plain HTTP. The only visible page title is “Become a Part Of BlockDAG Network | Buy BDAG Coins & Miners,” directly referencing the BlockDAG brand and suggesting a cryptocurrency offering.
Analysis of the page content classifies the activity as a crypto‑scam that impersonates BlockDAG and employs a Wallet Connect abuse kit, a known method for draining cryptocurrency wallets. The domain appears on two public security blocklists and has been blocked by both PhishDestroy and ScamSniffer. VirusTotal scanning shows four of ninety‑three security vendors flag the domain, reinforcing the malicious assessment.
As of the report date, July 25 2026, the site is taken offline, but the infrastructure remains observable. Defenders should continue to block the domain at network perimeter, monitor the associated IP address for any re‑use, and add the domain to internal threat intelligence feeds. Organizations using BlockDAG branding should verify any unsolicited communications referencing BDAG coins or miners against official channels, and users should be warned that any request to connect a wallet via the claimed site is likely fraudulent.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='claim.vestingblockdag.network', port=80): Max retries exceeded with url: / (Caused by NewC
For the registrable domain vestingblockdag.network behind this subdomain, 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:20 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.
Last analyzed Previous stored snapshot: 2 detections
G-Data
Sophos
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
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-02-27 02:01:37 UTC
VirusTotal scanner detections updated from 2 to 5. Added scanner alerts: ADMINUSLabs, Gridinsoft, SOCRadar.
Domain Status Transition2026-02-27 02:01:37 UTC
Domain state transitioned from alive to dead.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
15 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)
