56m[.]me

PhishDestroy first observed 56m.me on Feb 26, 2026. The captured page title is “1”. Current evidence score: 56/100 (high).

Positive findings are stored from 2 sources: VirusTotal and Cloudflare Radar. VirusTotal recorded 2 detections among 93 engines: CRDF, Gridinsoft on Feb 25, 2026 at 00:58 UTC. Cloudflare Radar classified the hostname as malicious and assigned the categories security threats and dga domains; its verdict timestamp was not retained. Non-positive and contextual checks: The external blocklist snapshot contained no matches on Aug 7, 2026 at 22:20 UTC. Google Safe Browsing returned no flag on Mar 2, 2026 at 21:03 UTC. URLScan completed without a malicious verdict (score 0) on Jul 29, 2026 at 03:20 UTC.

HTTP 502 was recorded on Aug 7, 2026 at 01:08 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 154.13.5.234 on AS35251 (ANTI-DDOS, US). The recorded endpoint location is Los Angeles, US. The stored server header is nginx. DOM analysis on Jul 29, 2026 at 04:13 UTC returned 56/100. The evidence archive retains 2 visual captures from PhishDestroy and URLScan.

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