mirka-sg.com was observed with an HTTP status 200 on 2026-10-13, which documents a successful response at that time. The domain is also listed in the publisher-owned PhishDestroy catalogue.
Recorded Evidence
OTX checked mirka-sg.com on 2026-10-13, recording 32 pulses as a reference. VirusTotal performed a scan on 2026-10-13, reporting 16 detections out of 92 total scanners. The domain was registered with DYNADOT LLC on 2025-08-27, and its first observation was on 2026-10-12.
Interpretation
The PhishDestroy internal listing contains a catalogue entry for mirka-sg.com, which is a publisher-owned measurement. VirusTotal provides a quantitative assessment of detections from multiple scanners, offering a broad technical perspective. OTX records pulse activity, which serves as an external intelligence reference for the domain. These sources collectively document the domain’s profile and timeline without asserting any specific outcome.
Recommended Actions
For mirka-sg.com, preserve the VirusTotal and OTX records for future comparison and reference. Retain the PhishDestroy catalogue entry as a publisher-owned listing. Use the HTTP status record to monitor any changes in response over time. These actions support ongoing review and contextual analysis based on the recorded evidence.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
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.
Last analyzed Previous stored snapshot: 16 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
Dr.Web
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
카스퍼스키
Lionic
Seclookup
소포스
URLQuery
VIPRE
Webroot
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-12 21:38:38 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 34.41.139.193.
위협 대응 Pipeline
발견
Analysis
Monitoring
8 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)
