VirusTotal
6 / 91 engine detections
PhishDestroy first recorded cfsw.online on 2026-02-26. Stored VirusTotal result: 6/91 engines flagged. Listed by external blocklists: ScamSniffer, Polkadot, Enkrypt, Codeesura.
Page title: “cfsw.online”
Stored VirusTotal result: 6/91 engines flagged. Listed by external blocklists: ScamSniffer, Polkadot, Enkrypt, Codeesura. Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
PhishDestroy analysis, earlier unreviewed version
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.
6 / 91 engine detections
5 threat-system alerts
Open reportMalicious
Open report2/15
23 community references
Open report63/100
Trust score, lower = worse
Open reportPage capture
Open reportSeparate stored monitor snapshot; does not replace the primary report record or establish current availability.
95 / 100 · heuristic score · 0 brand references · 1 classification
Content heuristic only; not the final score
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Narrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| OpenPhish | cfsw.online/ | phishing | Phishing - Generic/Spear Phishing |
| Cloudflare DNS | cfsw.online | malicious | Sinkholed |
| DNS0 Zero | cfsw.online | malicious | Sinkholed |
| Hagezi Threat Feed | cfsw.online | malicious | Sinkholed |
| DigiCert UltraDNS | cfsw.online | malicious | Sinkholed |
PhishDestroy rates cfsw.online as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-02-26. Stored VirusTotal result: 6/91 engines flagged. Listed by external blocklists: ScamSniffer, Polkadot, Enkrypt, Codeesura. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on cfsw.online. A confirmed blockchain transaction cannot be reversed.
Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.
Last checked
85c8a4356feac79b115dc95f440c4ccea0ce1297fcbcb670dd890185564d6c56 · 3418 bytes 2af286acb4af3f27c022038f03889e9207b71242245e645f6b93c087761e32c4 · 25911 bytes 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.
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.
failed-whois-verification.namecheap.comLocation describes the IP network.
*.cfsw.onlinecfsw.onlineSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The domain no longer resolves in DNS.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 5 SHA-256 hashes: 5 URLScan scan:
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 05:57 UTC.
Open this scan on URLScan 0199bcc3-452f-75a8-a1cd-672004f76364 ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
The site did not answer our scanner (host unreachable).
cfsw.online Source: domain_monitor. This stored snapshot does not establish current availability.
Recorded events: 18. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
Reported 157 d 8 h after registration
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.
Download all records as JSON| ID | Stored data |
|---|
Reported by 1 community member, first seen 2025-10-07
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
cfsw.online)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.