Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
The domain claimblockchainfx-io.live was observed in a PhishDestroy internal listing on 2026-10-13, documenting its inclusion in the publisher’s catalogue. A performance score of 68 was also measured for the domain during the same period, providing a technical indicator for that date.
Recorded Evidence
VirusTotal checked claimblockchainfx-io.live on 2026-10-13, reporting 0 detections from 92 scanners. PhishDestroy internally listed the domain on 2026-10-13. The domain was registered with NICENIC INTERNATIONAL GROUP CO., LIMITED on 2026-09-08. Pagespeed recorded a performance score of 68 for the domain on 2026-10-13.
Interpretation
PhishDestroy contains a listing for claimblockchainfx-io.live, which records its presence in the publisher’s internal catalogue. VirusTotal provides a measurement of external scanner detections, documenting the domain’s status across multiple security tools. The evidence from these sources allows for comparison of technical and security-related records from different perspectives.
Recommended Actions
For claimblockchainfx-io.live, retain the VirusTotal record and PhishDestroy internal listing for future reference and comparison. Preserve the performance score observation to support ongoing technical reviews. Use these documented records to inform subsequent checks and evaluations of the domain.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
캡처 라우팅
Local보관됨 2026-10-13 14:56:25 UTC
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
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.
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.
Values retained by the collector; long values may be shortened during collection.
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-13 13:00:02 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 104.21.30.51.
위협 대응 Pipeline
발견
Analysis
Monitoring
6 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.
Registrar Context: NiceNIC
Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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.
(RU)
PhishDestroy Investigation
