Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
The domain dydx.monster was registered on January 26, 2026 through NICENIC INTERNATIONAL GROUP CO., LIMITED and resolves to the IPv6 address 2606:4700:3033::ac43:b5f1, which is announced by AS13335 Cloudflare, Inc. in the United States. The site returns a HTTP 404 Not Found page title, indicating that the host is currently serving an error page rather than an active phishing landing page. Analysis of the SSL certificate shows a WE1 issuance, but no additional certificate details are available. The infrastructure received a Gridinsoft trust score of 0 out of 100, signaling a complete lack of trust.
Reputation services have placed the domain on three security blocklists, and it is explicitly blocked by PhishDestroy, MetaMask, and SEAL. VirusTotal scans report that three of ninety‑three security vendors flagged the domain, corroborating its malicious nature. The threat profile is identified as a crypto scam that impersonates the dYdX brand, aligning with the listed brand target. Current status is offline, suggesting the operator has withdrawn the site, but the registration and hosting details remain observable.
Defenders should continue to block the domain at network perimeter and endpoint layers, monitor the registrar for any changes, and add the IPv6 address to threat‑intel feeds. Because the site presently serves a 404 response, content‑level indicators are unavailable; therefore, further investigation should focus on passive DNS, certificate transparency logs, and any future re‑activation attempts. Maintaining awareness of the associated blocklists and ensuring that crypto‑wallet extensions such as MetaMask enforce their own blocklists will help mitigate residual risk from this infrastructure.
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='dydx.monster', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("S
DOM Analysisanalyzed 2026年3月24日score 78/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 outcomeRegistration hold observedreason: Registrar clientHold95% confidence
AttributionNICENIC INTERNATIONAL GROUP CO., LIMITEDmechanism: Registrar clientHoldsource: Rdap Status Collector
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Registrar clientHold
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 10:50:20 UTC
RDAP registrationRegistrar clientHoldNICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765RDAP HTTP 200source: Rdap Status CollectorclientDeleteProhibitedclientHoldclientTransferProhibitedexpires 2027-01-26 23:59:59 UTCchecked 2026-10-11 03:54:05 UTC
Registrar action markerverified clientHold markerNICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765causal link to our report not established
Observed timelinelast reachable: 2026-05-17 18:19:41 UTCcurrent episode first observed: 2026-08-05 01:45:38 UTCobserved RIP window: 2026-05-17 18:19:41 UTC → 2026-08-05 01:45:38 UTC · 1,903.43hmidpoint estimate ≈ 2026-06-26 10:02:39 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.
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
(RU)
PhishDestroy Investigation
