As of 2026-10-11, xrplatform.live was blocked by MetaMask and SEAL external blocklists. Additionally, the domain appeared in two external blocklists, providing further context for its recorded status.
Recorded Evidence
On 2026-10-11, xrplatform.live was referenced in the MetaMask and SEAL external blocklists. The domain was included in four OTX pulses as of the same date. Internal records from PhishDestroy documented a listing for xrplatform.live on 2026-10-11. The registrar was Dynadot Inc, and the SSL certificate was issued by Let's Encrypt / YE1, with the certificate scanned on 2026-10-11.
Interpretation
The OTX record for xrplatform.live contains measurements of its inclusion in four distinct pulses, which are collections of security intelligence observations. MetaMask and SEAL blocklist entries document that the domain was referenced by those external sources as part of their monitoring. The PhishDestroy internal listing expands the scope of evidence, offering another perspective on the domain's recorded status.
Recommended Actions
For xrplatform.live, preserve the OTX pulse records and the MetaMask and SEAL blocklist entries for ongoing comparison. Reference the PhishDestroy listing alongside other source records to track any new observations. Continue to review updated evidence from these sources to ensure a comprehensive record for xrplatform.live.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
등록 정보생성됨 2026년 10월 9일 (2d · Brand New!)—Expires 2027년 10월 9일
HTTP 상태302 Found (Temporary)
기술 세부 정보Provenance & timestamps
최초 발견2026년 10월 11일
DOM Analysisanalyzed 2026년 10월 11일score 90/1004 brand signals
Submitted URLhttp://xrplatform.live/
Favicon Hash
사건 ID
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-11 11:02:01 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 11:02:01 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-11 08:41:35 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.169.2.
위협 대응 Pipeline
발견
Analysis
Notifications
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
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)
