xxnfc[.]com

PhishDestroy first observed xxnfc.com on Nov 5, 2025. The captured page title is “Sorry, the website has been stopped”. Current evidence score: 100/100 (critical).

Positive findings are stored from 4 sources: VirusTotal, CryptoFirewall, DNS security resolvers, and Cloudflare Radar. VirusTotal recorded 19 detections among 95 engines: ADMINUSLabs, alphaMountain.ai, BitDefender, Certego, CyRadar, ESET, ESTsecurity, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, Lionic, Seclookup, SOCRadar, Sophos, Trustwave, Viettel Threat Intelligence, VIPRE on Feb 23, 2026 at 06:19 UTC. CryptoFirewall listed the hostname in the separate external-blocklist snapshot on Aug 8, 2026 at 06:20 UTC. DNS security checks returned 6 blocking results across 14 tested policies: Cloudflare Family, Cloudflare Security, Control D Adblock, Control D Family, Control D Malware, Quad9 Secure; no observation timestamp was retained. Cloudflare Radar classified the hostname as malicious and assigned the categories security threats and malware; its verdict timestamp was not retained. Non-positive and contextual checks: Gridinsoft assigned a trust score of 1/100 (Suspicious); no observation timestamp was retained. AlienVault OTX listed 5 community pulse references (not vendor detections) on Mar 1, 2026 at 18:36 UTC. URLQuery recorded no positive detection; no observation timestamp was retained. Google Safe Browsing returned no flag on Mar 2, 2026 at 20:21 UTC. URLScan completed without a malicious verdict (score 0) on Jul 29, 2026 at 03:35 UTC. PhishStats returned no feed match on Mar 1, 2026 at 19:14 UTC.

HTTP 502 was recorded on Aug 7, 2026 at 01:29 UTC; content was unavailable. Registration records for the domain list Gname.com Pte. Ltd. as the registrar and May 15, 2025 as the creation date. At collection time, the hostname resolved to 123.254.106.151 on AS55933 (CLOUDIE-AS-AP Cloudie Limited, HK). The recorded endpoint location is Tung Chung, HK. The stored server header is nginx. DOM analysis on Mar 11, 2026 at 09:23 UTC returned 0/100; the source detections above were recorded separately. The evidence archive retains 2 visual captures from PhishDestroy and URLScan.

The content indicators and 4 positive source findings support the current phishing classification. The stored fields do not identify an impersonated brand or victim interaction.