Analysis of the domain dydx-trades.online indicates a confirmed brand-impersonation threat targeting dYdX, a decentralized cryptocurrency exchange. Registered on August 16, 2025, through HOSTINGER operations, UAB, this domain currently resolves to an IPv6 address (2600:1901:0:84ef::) hosted on Google LLC's infrastructure (AS396982). The site was operational until recently, presenting a page title unrelated to cryptocurrency: 'Professional Cleaning and Maintenance Services | dydx.' This mismatch between the domain name and page content raises immediate red flags, as legitimate dYdX services would not associate with cleaning services. No SSL certificate was detected, increasing the risk of unencrypted data transmission.
Security vendors have flagged the domain, with three out of 95 engines on VirusTotal identifying malicious activity. Additionally, the domain appears on at least one security blocklist and is blocked by PhishDestroy. The use of DNS-parking nameservers (ns1.dns-parking.com, ns2.dns-parking.com) is atypical for a legitimate financial service and aligns with known phishing infrastructure patterns. While the domain is currently offline, defenders should treat it as an active threat vector.
Organizations are advised to block the domain at the DNS and firewall levels, monitor for related subdomains or IP associations, and alert users to the impersonation risk. Given the domain's registration age and recent takedown, threat actors may attempt to re-deploy it or spin up similar domains. No concrete evidence links this domain to a specific scam kit or payload, but the combination of brand impersonation, unrelated page title, and hosting on a major cloud provider suggests a deliberate attempt to deceive users into disclosing credentials or transferring cryptocurrency.
DOM Analysisanalyzed 2026年3月24日score 10/1001 brand signal
Submitted URLhttp://dydx-trades.online/
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-19 01:08:20 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-04-22 04:25:08 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-22 04:25:08 UTC → 2026-09-30 16:14:55 UTC · 3,875.83hmidpoint estimate ≈ 2026-07-11 22:20:01 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.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='dydx-trades.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
dydx-trades.online
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
(LT)
