The domain luxkazo.com was first observed on 2026-10-10, with a VirusTotal scan on that date documenting zero detections from 92 total scanners. The domain also appeared in the PhishDestroy internal listing, providing a publisher-specific record of its presence in security intelligence sources.
Recorded Evidence
On 2026-10-10, VirusTotal checked luxkazo.com and recorded zero detections out of 92 scanners. The domain was listed in the PhishDestroy internal catalogue on the same date. Registration records show luxkazo.com was registered with GMO Internet Group, Inc. d/b/a Onamae.com on 2026-10-03.
Interpretation
The VirusTotal record for luxkazo.com contains a measurement of how many external security scanners detected issues on the domain at the time of observation. The PhishDestroy internal listing documents the domain's inclusion in a publisher-maintained catalogue, which serves as a separate type of technical reference. These sources together provide a multi-faceted view of the domain's recorded status on their respective dates.
Recommended Actions
Retain the VirusTotal scan results and the PhishDestroy internal listing as reference points for luxkazo.com in future reviews. Compare these source records to any new security intelligence or scanner results that may arise for the domain.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
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-11 10:00:49 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:00:49 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-10 05:24:09 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 172.67.167.126.
위협 대응 Pipeline
발견
Analysis
Monitoring
5 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.
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.
