cryptoamlcontrol[.]com

PhishDestroy first recorded cryptoamlcontrol.com on Aug 2, 2026. This English evidence brief is rebuilt from the current structured observations stored for the report. The current evidence score, computed from those stored observations, is 65/100.

The latest stored availability state is “Last known active” on Aug 2, 2026 at 11:03 UTC. No conclusive HTTP response is stored, so current availability remains unverified.

VirusTotal returned 0 detections from 91 scanners in the stored check on Aug 2, 2026 at 06:27 UTC. A zero-vendor result is not a safety verdict. The independent blocklist snapshot recorded 1 match (ScamSniffer) across 10 configured external sources on Aug 2, 2026 at 10:20 UTC. PhishDestroy's own listing is excluded from that count.

Other stored evidence. Google Safe Browsing stored no positive flag on Aug 2, 2026 at 06:27 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 0 pulse references on Aug 2, 2026 at 06:28 UTC. OTX pulses are community-intelligence references, not vendor verdicts. The Spamhaus DBL snapshot stored no positive result on Aug 2, 2026 at 06:30 UTC. That result is not evidence of safety. A URLScan capture is stored from Aug 2, 2026 at 06:29 UTC.

Stored context lists registrar NAMECHEAP INC, IP address 37.221.66.44, registration date Dec 19, 2025, apparent target Binance. Except for the registration date, these fields do not share a source timestamp in this report and may change.

Treat these as stored, time-bound observations rather than a live safety guarantee. Source verdicts and reachability can change, and zero or missing vendor matches never prove that a domain is safe. Avoid interacting with the domain while uncertainty remains, and use the appeal process if this report is inaccurate.