The domain ofibive.digital is identified as a high-risk phishing infrastructure specifically designed for brand impersonation targeting Argent, a cryptocurrency wallet service. As of the latest assessment, the domain has been taken offline, though prior activity indicates malicious intent through deceptive page elements, including the title 'TwisProfit.' Analysis of the domain reveals multiple technical indicators of compromise. The domain was flagged by 20 of 95 security vendors on VirusTotal, and it appears on three distinct security blocklists. Registered on October 7, 2025, through PDR Ltd. d/b/a PublicDomainRegistry.com, the domain resolved to the IP address 188.114.96.3, hosted on AS13335 Cloudflare, Inc. infrastructure in the United States. Notably, the domain lacked an SSL certificate, a common red flag in phishing operations. Additional detection sources include PhishDestroy, MetaMask, and SEAL, further corroborating its malicious classification. Given the domain's current offline status, immediate threats are mitigated; however, residual risks may persist. Organizations and users are advised to block the domain across all security layers, including DNS filters and endpoint protection systems. Security teams should monitor for related infrastructure registered under the same registrar or resolving to the same IP range. Users who interacted with the domain prior to its takedown should assume credential exposure and initiate account recovery protocols, including password resets and multi-factor authentication enforcement for Argent-related services.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='ofibive.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
DOM Analysisanalyzed 2026年4月23日score 10/1004 brand signals
Submitted URLhttp://ofibive.digital/
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-11 01:09:33 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-06-16 22:16:04 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-16 22:16:04 UTC → 2026-09-30 16:14:55 UTC · 2,537.98hmidpoint estimate ≈ 2026-08-08 19:15:29 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.
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.
(IN)
