xahdhwy.com received an HTTP status 503 response on 2026-10-12, documenting a recorded server-side condition at that time. Additionally, Google Safe Browsing flagged the domain for social engineering threats on the same date.
Recorded Evidence
OTX documented three pulses referencing xahdhwy.com as of 2026-10-12. VirusTotal recorded 10 detections out of 92 scanners on 2026-10-11. Google Safe Browsing flagged the domain for social engineering on 2026-10-12. The domain was listed in the PhishDestroy internal catalogue as of 2026-10-12. The registrar was Gname.com Pte. Ltd., and registration was recorded on 2020-10-01.
Interpretation
The PhishDestroy internal listing contains a catalogue entry for xahdhwy.com, which is a type of publisher-owned record. VirusTotal provides a measurement of detections from multiple scanners, offering insight into the domain's profile across different security vendors. OTX records pulses, which are references to the domain in threat intelligence collections. These observations collectively document a range of recorded security findings from distinct sources, each with its own scope and methodology.
Recommended Actions
For xahdhwy.com, preserve the records from VirusTotal, OTX, Google Safe Browsing, and the PhishDestroy internal catalogue for ongoing comparison. Review future HTTP status responses and threat intelligence entries to track any changes in the domain’s recorded evidence. Maintain a separate archive of each dated source record to support consistent monitoring and assessment.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
Latest HTTP observation알 수 없음Origin unreachableHttp 5xx20%2026-10-12 10:00:35 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.
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.
Status Check2026-10-12 09:56:53 UTC
Telemetry event observed.
Threat First Observed2026-10-12 09:56:09 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 172.65.211.209.
위협 대응 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.
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.
(SG)
