This domain, cfsw.online, is currently flagged as an active high-risk phishing site targeting user credentials. Analysis indicates the domain was registered on February 21, 2026, through a major registrar, with no SSL certificate deployed, which is atypical for legitimate services handling sensitive information. The domain resolves to IP address 131.153.147.90, hosted on an autonomous system associated with a provider known for bulletproof hosting, further elevating infrastructure concerns. Infrastructure analysis reveals the domain uses nameservers linked to enforcement-resistant configurations, specifically verify-contact-details.namecheap.com and failed-whois-verification.namecheap.com, which are commonly observed in domains attempting to evade standard abuse reporting mechanisms. The domain is blocked by five security blocklists, including PhishDestroy and ScamSniffer, and is flagged by seven out of ninety-five security vendors on a widely used threat intelligence platform. The HTTP status returns a 200 response, indicating the site is operational and actively serving content, though the exact nature of the page remains unconfirmed beyond its reported title, cfsw.online. While the domain’s page title does not explicitly reveal a targeted brand or service, the combination of missing encryption, recent registration, and blocklist presence strongly suggests a credential harvesting operation. The lack of SSL is particularly notable, as it exposes any submitted data to interception during transmission. Defenders should treat this domain as hostile and implement immediate blocking at the network and endpoint levels. Additional monitoring of related infrastructure, particularly the hosting IP and nameserver patterns, is recommended to identify potential lateral movement or emerging campaigns using similar tactics.
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
(US)
