The domain etherex.financial is a phishing site engaged in brand impersonation targeting Ethereum users. It presents itself as a legitimate Ethereum-related service to deceive victims into disclosing sensitive information or transferring assets. No crypto drainer kit was detected, but the site poses an elevated risk due to its fraudulent representation of the Ethereum brand. As of the latest verification, etherex.financial has been taken offline.
Technical indicators confirm the domain's malicious nature. etherex.financial was flagged by 1 of 95 security vendors on VirusTotal, including Gridinsoft, and appears on 1 security blocklist (PhishDestroy). Registered through Dynadot LLC on February 21, 2026, the domain resolves to the IP address 104.21.67.134, hosted on Cloudflare's infrastructure (AS13335). The SSL certificate is issued by Google Trust Services / WE1, and the observed page title was 'etherex.financial | 525: SSL handshake failed'. Nameservers are brenna.ns.cloudflare.com and hassan.ns.cloudflare.com, and the site utilized Cloudflare and HTTP/3 technologies.
Victims of etherex.financial should immediately change any passwords or credentials entered on the site and enable two-factor authentication (2FA) on all accounts. Monitor financial and crypto accounts for unauthorized transactions, and consider revoking any token approvals granted to unknown or suspicious services. Report the phishing domain to the impersonated brand (Ethereum), the registrar (Dynadot LLC), and platforms like Google Safe Browsing or PhishTank to aid in takedown efforts.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='etherex.financial', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
DOM Analysisanalyzed 2026年7月9日score 71/1001 brand signal
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.
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:30:25 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-15 22:17:56 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-15 22:17:56 UTC → 2026-09-30 16:14:55 UTC · 353.95hmidpoint estimate ≈ 2026-09-23 07:16:25 UTC · precision 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.
技术 · 2 identified
Cloudflare
CDN
Web infrastructure and security company providing CDN, DDoS mitigation, and DNS services.
Last analyzed Previous stored snapshot: 3 detections
alphaMountain.ai
CRDF
Gridinsoft
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.
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)
