crypto619[.]com

PhishDestroy first recorded crypto619.com on Jul 23, 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 90/100.

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

VirusTotal returned 5 detections from 91 scanners in the stored check on Aug 1, 2026 at 02:05 UTC. The independent blocklist snapshot recorded 2 matches (MetaMask, SEAL) across 10 configured external sources on Aug 2, 2026 at 18:20 UTC. PhishDestroy's own listing is excluded from that count.

Other stored evidence. Google Safe Browsing stored no positive flag on Jul 23, 2026 at 13:37 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 0 pulse references on Jul 23, 2026 at 13:40 UTC. OTX pulses are community-intelligence references, not vendor verdicts. The Spamhaus DBL snapshot stored no positive result on Jul 23, 2026 at 14:30 UTC. That result is not evidence of safety. A stored Cloudflare Radar snapshot labels the domain malicious. No source check timestamp is stored for this field. A URLScan capture is stored from Jul 23, 2026 at 13:37 UTC.

Stored context lists registrar 22net, Inc., IP address 34.177.106.6, registration date Jul 8, 2026. 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.