nickles[.]cc

PhishDestroy first observed nickles.cc on Feb 26, 2026. The captured page title is “Message”. Current evidence score: 95/100 (critical).

Positive findings are stored from 3 sources: VirusTotal, Spamhaus DBL, and Cloudflare Radar. VirusTotal recorded 18 detections among 93 engines: ADMINUSLabs, alphaMountain.ai, BitDefender, Cluster25, CyRadar, DNS8, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Kaspersky, Lionic, Phishing Database, Seclookup, SOCRadar, Sophos, VIPRE, Webroot on Feb 25, 2026 at 01:00 UTC. Spamhaus DBL: DBL_PHISH on Jul 14, 2026 at 06:34 UTC. Cloudflare Radar classified the hostname as malicious and assigned the categories phishing, malware, and security threats; its verdict timestamp was not retained. Non-positive and contextual checks: AlienVault OTX listed 15 community pulse references (not vendor detections) on Mar 1, 2026 at 05:06 UTC. The external blocklist snapshot contained no matches on Aug 7, 2026 at 22:20 UTC. URLQuery recorded no positive detection; no observation timestamp was retained. Google Safe Browsing returned no flag on Mar 2, 2026 at 20:49 UTC. URLScan completed without a malicious verdict (score 0) on Jul 29, 2026 at 03:20 UTC. PhishStats returned no feed match on Mar 1, 2026 at 14:09 UTC.

HTTP 502 was recorded on Aug 7, 2026 at 01:21 UTC; content was unavailable. The recorded creation date for the domain is Feb 21, 2026. Registration preceded first observation by 5 days. At collection time, the hostname resolved to 217.60.62.75 on AS56971 (AS56971 CGI GLOBAL LIMITED, HK). The recorded endpoint location is Helsinki, FI. The stored server header is nginx. DOM analysis on Jul 29, 2026 at 04:13 UTC returned 83/100. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. TLS metadata lists R12 as the certificate issuer with validity through Jun 26, 2026.

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