This domain, www.fwc26coin.com, is currently active and has been classified as a high‑risk generic phishing site. The registration record shows it was created on 08 March 2026 through Namecheap Inc, and the authoritative nameservers are dns1.registrar-servers.com and dns2.registrar-servers.com. DNS resolution points to the address 216.198.79.1, which is the sole hosting endpoint observed for this infrastructure. The domain appears on one public blocklist and is specifically listed by the PhishDestroy feed, confirming that at least one security‑focused organization has taken mitigation action against it.
VirusTotal analysis reports that 1 of 91 scanned security vendors flagged the domain, indicating that at least one detection engine identified malicious characteristics. No additional public signals such as Google Safe Browsing, OTX pulldowns, SSL certificate details, HTTP response codes, or trust‑score metrics have been published for this site at the time of analysis. Consequently, the full extent of the phishing campaign—targeted brand, page content, or credential‑ harvesting mechanisms—remains unknown.
Defenders should block or sinkhole 216.198.79.1 at the network perimeter, add www.fwc26coin.com to local and cloud‑based URL filtering lists, and monitor DNS queries for the associated nameservers. Continuous re‑scanning on VirusTotal and periodic checks against emerging blocklists are advised to capture any changes in detection status. Organizations receiving phishing reports that reference this domain should advise users to avoid clicking any links and to report the incident to their incident response team.
DOM Analysisanalyzed 2026年8月4日score 71/10010 brand signals
Submitted URLhttp://www.fwc26coin.com/
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.
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.
(IS)
