The domain digowex.com was first observed on 2026-10-12, with a recorded PhishDestroy internal listing on the same date. Additionally, the domain was registered recently, on 2026-10-10, which may be relevant for timeline comparisons.
Recorded Evidence
VirusTotal checked digowex.com on 2026-10-11 and documented 0 detections out of 92 total scanners. OTX referenced the domain in 4 pulses as of 2026-10-12. The domain is listed in the PhishDestroy internal catalogue as of 2026-10-12, and its registrar is DYNADOT LLC.
Interpretation
PhishDestroy contains a listing for digowex.com, which is a catalogue reference that records the domain's presence in its internal database. VirusTotal's measurement provides a snapshot of detection results from multiple scanners, offering a technical perspective on the domain's status at the time of its check. The timeline of these records, spanning from registration to observations within a few days, allows for comparison of the domain's early history across different intelligence sources.
Recommended Actions
For digowex.com, retain the VirusTotal detection snapshot and OTX pulse records for ongoing reference. Preserve the PhishDestroy internal listing to compare with future catalogue entries. Use these dated records to monitor any changes in external intelligence or detection results over time.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-12 10:00:33 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-12 10:00:33 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.
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 09:14:15 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 188.114.96.1.
위협 대응 Pipeline
발견
Analysis
Monitoring
6 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.
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026년 10월 12일
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
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)
