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.
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 DetectedJun 23, 2026
DOM Analysisanalyzed Jun 23, 2026score 71/1007 brand signals
IoC Extractionscanned Jul 29, 20260 wallet · 1 Telegram IoC
Submitted URLhttps://www.ocm.systems/
Favicon Hash
Case ID
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
82.25.96.230
Network ASN
AS47583
Organization
Hostinger International Limited
Observed location
Frankfurt am Main, DE
Server header
LiteSpeed
Nameservers 1
ns2.dns-parking.com
Mail routing 2 MX records
mx1.hostinger.compriority 5
mx2.hostinger.compriority 10
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YE2
Valid from
2026-06-10 03:46:24
Valid until
2026-09-08 03:46:23
Hostname coverage
Stored certificate expired or unverified
Validity
Stored certificate expired
Collection time
2026-06-23 07:00:04 UTC
Collection source
PhishDestroy collector
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 inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:00:15 UTC
RDAP registrationUnknown
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.
Threat Response Pipeline
Discovery
Analysis
Monitoring
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 26, 2026
Time to First Unavailability
5 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.
4 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 →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · ocm.systems
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.
(LT)
