This domain, www.ozakagi.network, is flagged as an active phishing site targeting users of the Across protocol, a cross-chain bridging platform. Analysis indicates the site presents itself under the page title 'Predictive AI Agents for Advanced Financial Intelligence,' though the exact content and functionality remain unconfirmed beyond this identifier. The domain is explicitly categorized as a wallet-connect phishing threat, suggesting it attempts to trick users into connecting cryptocurrency wallets to malicious smart contracts or interfaces designed to drain funds. Infrastructure analysis reveals the domain resolves to 216.24.57.251, hosted under AS397273 (Render), and was registered through the provider identified as RS-1125. The SSL certificate is issued by Let's Encrypt (R12), a common choice for both legitimate and malicious sites. While the domain currently returns an HTTP 200 status, no nameservers were detected in the available data, which may indicate an attempt to obscure DNS-level tracking or a misconfiguration. Security vendors have detected this domain, with 8 out of 95 flagging it as malicious, and it appears on at least one security blocklist. The domain has been linked to a single threat intelligence pulse in AlienVault OTX, reinforcing its classification as a targeted phishing operation. Defenders should treat this domain as high-risk, particularly for users interacting with the Across protocol or similar DeFi platforms. Recommended actions include blocking the domain and IP at the network level, alerting users to the wallet-connect phishing risk, and monitoring for related infrastructure or certificate reuse. Given the domain's active status as of July 12, 2026, continued vigilance is advised until takedown or further evidence of compromise is confirmed.
Extracted from stored page analysis
Observed indicators
1 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-12352.invalid', port=80): Max retries exceeded with url: / (Caused by N
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedOct 3, 2025
DOM Analysisanalyzed Apr 23, 2026score 83/1006 brand signals
IoC Extractionscanned Jul 29, 20261 wallet · 1 Telegram IoCs
Submitted URLhttps://www.ozakagi.network/
Favicon Hash
ICANN OVERSIGHT
Accreditation and RAA context
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.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:31:00 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-23 02:12:36 UTC
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.
Google PageSpeed Insights — mobile performance audit of duplicate-disabled-12352.invalid· checked Apr 26, 2026
64
Needs Work
Performance
FCP
3.23s
First Contentful Paint
LCP
7.13s
Largest Contentful Paint
CLS
0.002
Cumulative Layout Shift
TBT
197ms
Total Blocking Time
SI
4.95s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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.
Domain Status Transition2026-09-25 01:31:11 UTC
Domain state transitioned from alive to dead.
Threat Response Pipeline
Discovery
Analysis
Monitoring
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
duplicate-disabled-12352.invalid detected and queued for full analysis
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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 25, 2026
Time to First Unavailability
5359 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
5 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches5
Same favicon hash or the same page title as this host.
