The domain ozakai.network, impersonating the brand "across," has a high threat score of 85/100 and is currently down or taken down. It has been flagged as malicious by 2 out of 95 security vendors, including CRDF and Gridinsoft, and is listed on 4 public blocklists, indicating significant recognition of its threat potential. Google Safe Browsing has not flagged this domain.
Registered with AMAZO-ZFRA, the domain's hosting IP is 35.157.26.135. It was first seen on 2025-09-24, suggesting it is a relatively new threat. The down status may indicate an active response to its malicious activities. Block the domain at the perimeter and submit a report to the registrar's abuse desk to mitigate any potential impact.
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.
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='ozakai.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
DOM Analysisanalyzed 2026年4月23日score 15/1006 brand signals
IoC Extractionscanned 2026年8月2日1 wallet · 1 Telegram IoCs
Submitted URLhttps://ozakai.network/
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-11 01:09:39 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-06-17 22:12:48 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-17 22:12:48 UTC → 2026-09-30 16:14:55 UTC · 2,514.04hmidpoint estimate ≈ 2026-08-09 07:13:51 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.
