The owner of the website is using a service to hide their identity on WHOIS According to Tranco this site has a low rank High number of suspicious websites on this server This website is very young and has a suspiciously high number of reviews This website is (very) young. We tried to analyze the content of the site but failed The website offers data-sensitive [financial] services hosted on a shared server.
This website has received mainly positive reviews The SSL certificate is valid
证据摘要
关键
VirusTotal
9/95
OTX
2 community refs
URLScan
Stored capture
This domain, blockchainfx.online, poses a high-risk brand impersonation threat targeting users of a well-known cryptocurrency platform. The site mimics the branding, design, and functionality of Blockchain.com, presenting itself as a decentralized crypto and multi-asset exchange under the name BlockchainFX. Such impersonation schemes are typically designed to deceive users into disclosing sensitive credentials, transferring digital assets, or installing malicious software. Given the domain’s active status and lack of security measures, visitors risk financial loss or unauthorized access to their crypto wallets and personal data. Analysis indicates this domain was registered on October 25, 2025, through HOSTINGER operations, UAB, a registrar frequently associated with fraudulent infrastructure. The site currently resolves to the IP address 216.24.57.1, hosted on AS397273 Render in the United States, and lacks a valid SSL certificate—a critical security gap for any financial or crypto-related service. VirusTotal reports that 9 out of 95 security vendors have flagged blockchainfx.online as malicious, with additional detections on four security blocklists, including PhishDestroy, Polkadot, Enkrypt, and Codeesura. The absence of encryption, combined with its presence on multiple threat intelligence feeds, reinforces the domain’s high-risk classification. If you have visited blockchainfx.online or interacted with its content, immediate action is required. Disconnect any connected wallets or devices from the internet and revoke any active sessions linked to the site. Scan your system for malware using updated security tools, and monitor all financial and crypto accounts for unauthorized transactions. Change passwords and enable multi-factor authentication on all related services. Report the domain to your wallet provider and relevant cybersecurity authorities to help prevent further exploitation. Users should verify all crypto-related communications through official channels only and avoid engaging with unsolicited links or platforms.
Extracted from stored page analysis
Observed indicators
1 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='blockchainfx.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionE
DOM Analysisanalyzed 2026年4月23日score 90/10017 brand signals
IoC Extractionscanned 2026年8月2日1 wallet · 1 Telegram IoCs
Submitted URLhttp://blockchainfx.online/
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.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:13:51 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-07-05 16:17:29 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-05 16:17:29 UTC → 2026-09-30 16:14:55 UTC · 2,087.96hmidpoint estimate ≈ 2026-08-18 04:16:12 UTC · precision very low · basis bounded
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.
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.
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.
(LT)
