elontwitter777.xyz was first observed in the evidence on 2026-10-10, with a VirusTotal scan documenting its detection status on that date. The domain is also referenced in a publisher-owned PhishDestroy internal listing, providing a catalogue entry for further review.
Recorded Evidence
VirusTotal checked elontwitter777.xyz on 2026-10-10, recording 6 detections out of 92 scanners. OTX documented three pulses for the domain as of 2026-10-12. The domain was registered on 2026-10-07, and its first observed date is 2026-10-10. PhishDestroy contains an internal listing for this domain, which is a publisher-owned catalogue entry.
Interpretation
PhishDestroy measures the domain's presence in its internal listing, offering a catalogue perspective. VirusTotal provides a quantitative record of detections, reflecting how multiple scanners evaluated elontwitter777.xyz. OTX documents intelligence pulses, which are entries related to the domain in external intelligence sources. These records span technical, intelligence, and catalogue data, allowing for comparison across distinct evidence types.
Recommended Actions
For elontwitter777.xyz, preserve the VirusTotal detection results and OTX pulse records for ongoing reference. Compare future catalogue entries from PhishDestroy with the current evidence. Use these records to inform subsequent reviews and maintain a consistent evidence trail for the domain.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
등록 정보생성됨 2026년 10월 7일 (5d · Brand New!)—Expires 2027년 10월 7일
HTTP 상태301 Moved Permanently
기술 세부 정보Provenance & timestamps
최초 발견2026년 10월 10일
DOM Analysisanalyzed 2026년 10월 13일score 98/100
Submitted URLhttp://elontwitter777.xyz/
Favicon Hash
ICANN OVERSIGHT
인증 및 RAA 상황
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
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-13 01:35:41 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-13 01:35:41 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.
Last analyzed First positive detection Previous stored snapshot: 6 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Gridinsoft
LevelBlue
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.
Threat First Observed2026-10-12 12:09:34 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 66.198.225.39.
위협 대응 Pipeline
발견
Analysis
Monitoring
9 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)
