The domain blockresolver.online has been identified as a crypto drainer phishing site, designed to compromise digital asset wallets and siphon cryptocurrency. Analysis indicates the domain is currently offline, though prior activity suggests it targeted users through deceptive wallet connection prompts or fake decentralized application interfaces. No specific brand impersonation has been confirmed, but the infrastructure aligns with known crypto-theft campaigns. Infrastructure analysis reveals the domain was registered on November 28, 2025, through Spaceship, Inc., a registrar frequently associated with high-risk domains. It resolves to the IP address 140.99.164.68, which has been linked to other malicious activities in recent threat intelligence reports. Detection metrics show the domain is flagged by 3 of 95 security vendors on VirusTotal and appears on 5 distinct security blocklists, including Codeesura, Polkadot, ScamSniffer, PhishDestroy, and Enkrypt. The Gridinsoft trust score for this domain is 0 out of 100, further corroborating its malicious classification. At present, blockresolver.online is offline, though domains of this nature often resurface under altered infrastructure. Users are advised to verify wallet connections exclusively through official platforms and to employ browser-based security extensions that block known phishing domains. Network administrators should update firewall rules to deny traffic to 140.99.164.68 and monitor for any re-registration attempts under similar naming conventions. Cryptocurrency holders should review wallet permissions and revoke access to any unfamiliar or suspicious applications.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='blockresolver.online', port=80): Max retries exceeded with url: / (Caused by NewConnection
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:03 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-05-22 08:10:57 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-05-22 08:10:57 UTC → 2026-09-30 16:14:55 UTC · 3,152.07hmidpoint estimate ≈ 2026-07-27 00:12:56 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.
Last analyzed Previous stored snapshot: 3 detections
alphaMountain.ai
Gridinsoft
SOCRadar
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-06-27 01:38:29 UTC
VirusTotal scanner detections updated from 1 to 3. Added scanner alerts: alphaMountain.ai. Resolved alerts: Trustwave.
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.
(US)
