www.ocm.systems was observed on 2026-07-12 and is classified as a high‑risk generic phishing domain. The site resolves to the IPv4 address 82.25.96.230, returns HTTP 200, and displays the page title “OCM — Open Compute Mastery | Decentralized AI & Compute”. Its TLS certificate is issued by Let’s Encrypt (identifier YE2), which may provide a veneer of legitimacy for unsuspecting victims.
Infrastructure analysis shows the domain is registered through Hostinger operations, UAB, and relies on the default parking nameservers ns1.dns-parking.com and ns2.dns-parking.com. The IP address maps to Germany and belongs to AS47583 Hostinger International Limited, a provider whose shared hosting environment is frequently abused for short‑lived malicious sites. Mail exchangers are mx1.hostinger.com (priority 5) and mx2.hostinger.com (priority 10), indicating that the domain can also be used for email‑based credential harvesting.
Threat intelligence indicates the domain is blocked by PhishDestroy and appears on one public security blocklist. VirusTotal scans report that 2 of 95 security vendors flagged the domain, and Gridinsoft assigns a trust score of 0 / 100, reinforcing the malicious assessment. Although the blocklist footprint is limited, the combination of a low trust score, vendor detections, and active blocking suggests ongoing abusive activity.
Defenders should treat www.ocm.systems as malicious. Immediate actions include adding the domain and its IP 82.25.96.230 to network deny lists, configuring email gateways to reject messages from its MX hosts, and monitoring DNS queries for the associated nameservers. SOC teams should also correlate authentication attempts against services that may be targeted by the phishing campaign, consider sinkholing the domain to disrupt attacker traffic, and maintain continuous re‑evaluation as the site remains active and could evolve its payloads.
Extracted from stored page analysis
Observed indicators
0 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='ocm.systems', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
DOM Analysisanalyzed 2026年6月23日score 71/1007 brand signals
IoC Extractionscanned 2026年7月29日0 wallet · 1 Telegram IoC
Submitted URLhttps://www.ocm.systems/
Favicon Hash
案件 ID
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.
Certificate fingerprint60d2d1acc757c69c42b1f5d97afff93c21517576ef1e0ff4f0d22c827e11afbcCertificate names · 1 SANs
ocm.systems
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-13 01:00:15 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-15 22:18:17 UTCcurrent episode first observed: 2026-09-30 16:26:51 UTCobserved RIP window: 2026-09-15 22:18:17 UTC → 2026-09-30 16:26:51 UTC · 354.14hmidpoint estimate ≈ 2026-09-23 07:22:34 UTC · precision 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.
Domain Status Transition2026-09-26 10:44:06 UTC
Domain state transitioned from alive to dead.
威胁响应 Pipeline
发现
Analysis
Monitoring
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.
(LT)
