탐지를 보고하는 보안 엔진: 2. 극도의 주의를 기울이십시오 — 자격 증명이나 개인 정보를 입력하지 마십시오.
보고서 요약
qanxing.com — 콘텐츠를 사용할 수 없음. 브랜드 사칭: Google; 사기 유형: Impersonation. 증거 요약: VirusTotal 2/92 (CRDF, SOCRadar); Google Safe Browsing flagged; Spamhaus DBL_ABUSED_PHISH; PhishDestroy score 80/100. 등록기관: DNSPod.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
qanxing.com returned an HTTP 404 status code on 2026-10-07, showing no content was available from the web server at that time. On the same date, the domain was also listed by OpenPhish, which is an external blocklist.
Recorded Evidence
Google Safe Browsing flagged qanxing.com for social engineering on 2026-10-07. VirusTotal reported 2 detections out of 92 scanners for the domain on 2026-10-07. OTX included qanxing.com in 3 pulses as of 2026-10-07. The registrar was DNSPod, Inc., and the domain was registered on 2022-01-26.
Interpretation
The records from OpenPhish, Google Safe Browsing, VirusTotal, and OTX show that several security sources noted qanxing.com on the same date. The HTTP 404 status only describes the web server's response at that specific time, while the security listings indicate attention from multiple monitoring services.
Recommended Actions
Retain all records from OpenPhish, Google Safe Browsing, VirusTotal, and OTX for qanxing.com for future comparison. Use these source observations to track any changes or new listings related to the domain.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
마지막 은폐 스캔
스캐너 메모:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='qanxing.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-11 01:33:45 UTC
RDAP registration알 수 없음
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: 2 detections
CRDF
SOCRadar
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.
Domain Status Transition2026-10-07 10:00:23 UTC
Domain state transitioned from alive to dead.
Status Check2026-10-07 08:04:49 UTC
Telemetry event observed.
Threat First Observed2026-10-07 08:04:17 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 154.9.24.78.
위협 대응 Pipeline
발견
Analysis
Monitoring
13 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.
최근에 저장된 확인 결과에 따르면 보고된 콘텐츠를 사용할 수 없습니다. 이는 변경의 원인이 누구인지, 원인이 무엇인지 확인하지 않습니다.
2026년 10월 7일
최초 이용 불가까지 걸린 시간
감지부터 사용할 수 없는 첫 번째 관찰까지 1 시간이 경과되었습니다.
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.
