VirusTotal
3 / 91 engine detections
Відкрити звіт“OCM — Open Compute Mastery | Decentralized AI & Compute”
домен у блоклистах: ocm.systems — Контент недоступний. Зведення доказів: VirusTotal 3/91 (Forcepoint ThreatSeeker, Gridinsoft, SOCRadar); PhishDestroy score…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
3 / 91 engine detections
Відкрити звітScan report
Відкрити звітno community references
Відкрити звітNo threat flag
Відкрити звітPage capture
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
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.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/+KFDQ6D4nMW8zODI0Stored page referenceIoC extraction recorded 2026-07-29 01:59:07 UTC
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.
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.
ns2.dns-parking.commx1.hostinger.compriority 5mx2.hostinger.compriority 10Location describes the IP network.
60d2d1acc757c69c42b1f5d97afff93c21517576ef1e0ff4f0d22c827e11afbcocm.systemsSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
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
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
Доступний→Недоступно
3/91 engine detections
View sourcePage captured
View sourceNo threat flag
View sourceocm.systems
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
ocm.systems)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Аналіз загроз за допомогою збереженого списку блокувань, WHOIS, DNS і загальнодоступних доказів сканування
Сканувати заразДодавайте підозрілі домени до нашої бази даних загроз — захищайте спільноту
ПовідомитиОстанні звіти про фішинг і помічені зміни доступності
ВідстежуватиСлідкуйте за актуальними загрозами або оскаржте цей запис, якщо вважаєте, що це помилкова тривога
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.