탐지를 보고하는 보안 엔진: 15. 극도의 주의를 기울이십시오 — 자격 증명이나 개인 정보를 입력하지 마십시오.
ABUSE NOTICE · 24H+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@omegatech.sc.
The latest stored availability evidence still shows the domain reachable; 2 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Elapsed since first report
2 days
Reports sent
1
Latest case ID
PD-20261009-A5A201
Current status
HTTP 200 at latest stored check
보고서 요약
zinovircenomira.com — 마지막으로 알려진 활성 (HTTP 200). 브랜드 사칭: Celer; 사기 유형: Impersonation. 증거 요약: VirusTotal 15/92 (alphaMountain.ai, BitDefender, CRDF, DNS8, ESET); URLQuery 2 det.; CF Radar malicious; PhishDestroy score 100/100. 등록기관: Dynadot.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
On 2026-10-09 zinovircenomira.com returned an HTTP 200 status, confirming a successful connection at that time. The domain’s page title was recorded as Zinovír Cenomíra — Algoritmická obchodní platforma pro investory during the same observation.
Recorded Evidence
On 2026-10-09 OTX recorded four pulses for zinovircenomira.com. VirusTotal detected 15 detections out of 92 scanners on 2026-10-07. The domain appeared in the PhishDestroy internal listing and was registered with Dynadot Inc on 2026-05-17. A PageSpeed performance score of 98 was measured on 2026-10-09.
Interpretation
The OTX pulses, VirusTotal detections, and PhishDestroy internal listing together provide external and internal security intelligence for zinovircenomira.com. These dated records allow a snapshot comparison of network and catalogue indicators without implying present status or intent.
Recommended Actions
Retain the OTX pulse references and VirusTotal detection results for zinovircenomira.com. Compare the PhishDestroy internal listing with the HTTP response record for future assessments. Use these dated records to inform further technical or security analysis of the domain.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation활성 콘텐츠Ordinary HTTP content served90%2026-10-11 10:41:59 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:41:59 UTClast content: 2026-10-11 10:41:59 UTC
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.
기술 · 3 identified
N
Node.js
Programming languages
Node.js is an open-source, cross-platform, JavaScript runtime environment that executes JavaScript code outside a web browser.
Express is a web application framework for Node.js, released as free and open-source software under the MIT License. It is designed for building web applications and APIs.
Last analyzed Previous stored snapshot: 15 detections
alphaMountain.ai
BitDefender
CRDF
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
카스퍼스키
Lionic
Seclookup
SOCRadar
소포스
VIPRE
사이트 성능 분석
Google PageSpeed Insights — mobile performance audit of zinovircenomira.com· checked Oct 9, 2026
98
Good
Performance
FCP
0.98s
First Contentful Paint
LCP
0.99s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.9s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
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.
Threat First Observed2026-10-09 03:09:07 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 158.94.210.119.
위협 대응 Pipeline
발견
Analysis
Notifications
Monitoring
11 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.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
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.
(US)
