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.
Cosa conteggiamo
Tempo trascorso dalla prima segnalazione di abuso archiviata alla prima osservazione che il contenuto non era disponibile. Ciò non ne stabilisce la causa.
Cosa contiene ogni rapporto
I record archiviati dei report in uscita possono fare riferimento a prove disponibili in quel momento, come verdetti dei fornitori, dati di registrazione, dettagli di hosting, classificazioni o screenshot. Questa pagina non deduce l'esatto carico utile consegnato, la ricevuta, la conferma o l'azione da parte di un destinatario.
Dettagli tecniciProvenance & timestamps
Rilevato per la prima volta23/06/2026
DOM Analysisanalyzed 23/06/2026score 71/1007 brand signals
IoC Extractionscanned 29/07/20260 wallet · 1 Telegram IoC
Submitted URLhttps://www.ocm.systems/
Favicon Hash
ID del caso
ICANN OVERSIGHT
Accreditamento e contesto 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.
Accountability draft
Nulla viene inviato automaticamente.
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
Nameserver 1
ns2.dns-parking.com
Mail routing 2 MX records
mx1.hostinger.compriority 5
mx2.hostinger.compriority 10
Location describes the IP network.
Certificato TLS
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 inattivoreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationSconosciutoProbe Inconclusive20%2026-10-19 01:00:16 UTC
RDAP registrationSconosciuto
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.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
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
ocm.systems
Risultato salvato
Cloaked / Filtered
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Le relazioni archiviate sono raggruppate in base all'attributo di corrispondenza esatta. Un fornitore o un registrar condiviso da solo non dimostra la proprietà comune.
Mappa delle infrastrutture · ocm.systems
Ogni riga rappresenta un motivo per cui un dominio è collegato a questo host. I nodi a dimensione intera indicano rilevamenti di VirusTotal, mentre quelli tratteggiati sono già offline. Di seguito è riportato l'elenco completo.
Registrati tramite lo stesso registrar. Un registrar serve milioni di clienti non collegati tra loro, quindi questo dato indica semplicemente un raggruppamento piuttosto che dimostrare un nesso.
4 evidence signal groups linked0 stored notification recordsContenuto non disponibile
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
Se hai inserito credenziali dell'account, informazioni personali o di pagamento oppure hai scaricato un file da questo dominio, agisci immediatamente. Di seguito sono riportate le risorse per aiutarti a segnalare l'incidente e proteggerti.
Attenzione ai truffatori che promettono il recupero dei fondi! I criminali possono contattare nuovamente le vittime fingendo di essere investigatori, avvocati o agenti di recupero. Non pagare commissioni anticipate né condividere credenziali.Scopri di più sulle frodi relative ai sussidi di recupero →
Template-based draft · optional AI wording assistance requires separate consent
Bozza assistita dall'intelligenza artificiale: i dettagli dell'incidente vengono elaborati dal fornitore di intelligenza artificiale · Controllalo e invialo tu stesso
After a phishing incident
Raccomandazioni e consigli per le vittime
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Cosa devo fare subito?
Urgente
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Modifica tutte le password — e-mail, account Exchange, qualsiasi servizio che utilizzi la stessa password
Abilita l'autenticazione a due fattori (2FA) utilizzando un'app di autenticazione (non via SMS). Disattiva il recupero tramite SMS
Carte congelate se hai inserito i tuoi dati bancari sul sito di phishing
Quali informazioni devo raccogliere per la mia relazione?
Linee guida dell'FBI
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Date e orari esatti — di ogni transazione e del primo contatto con il truffatore
Schermate — siti web truffaldini, messaggi in chat, e-mail, transazioni tramite portafoglio digitale, social media
Tutti gli URL e i domini utilizzato dal truffatore (tra cui ocm.systems)
Comunicazioni — e-mail, SMS, numeri di telefono, nomi utente utilizzati dal truffatore
Anche se non conosci tutti i dettagli — sporgere comunque denuncia. Anche le informazioni parziali sono comunque utili alle indagini.
A chi devo segnalare la truffa?
FBI IC3 — Internet Crime Complaint Center (sistema di segnalazione federale degli Stati Uniti)
Europol — Segnalazioni relative alla criminalità informatica in Europa (UE)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Polizia locale — crea un documento ufficiale, anche se non è in grado di agire immediatamente
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Siti web fasulli — cloni perfetti, al pixel, di siti legittimi con domini leggermente modificati
Macellazione dei suini — fiducia conquistata nel corso di settimane tramite Telegram/WhatsApp/app di incontri, per poi rubare i soldi
Truffe legate al recupero dei fondi — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
Truffe basate sull'intelligenza artificiale — i deepfake, il phishing automatizzato e i siti generati dall’intelligenza artificiale rendono più difficile individuare le frodi
Come posso proteggermi in futuro?
Aggiungi i siti ufficiali ai preferiti — Non cliccare mai sui link contenuti nelle e-mail, nei messaggi diretti o negli annunci pubblicitari
Verifica i domini — controllare PhishDestroy prima di interagire. Verifica l'HTTPS, l'ortografia e l'età del dominio
"Troppo bello per essere vero" = truffa — rendimenti garantiti, testimonial di personaggi famosi, scadenze urgenti
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
(LT)
