junofex[.]com

PhishDestroy first recorded junofex.com on Jun 17, 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 71/100.

The latest stored availability state is “Reachable · access restricted” (HTTP 403) on Aug 2, 2026 at 10:15 UTC. This is a reachability snapshot, not proof of the cause of any outage, restriction, or status change.

VirusTotal returned 2 detections from 91 scanners in the stored check on Jul 18, 2026 at 18:45 UTC. The independent blocklist snapshot recorded 2 matches (MetaMask, SEAL) 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 Jun 25, 2026 at 18:15 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 0 pulse references on Jun 17, 2026 at 16:12 UTC. OTX pulses are community-intelligence references, not vendor verdicts. The Spamhaus DBL snapshot stored no positive result on Jul 18, 2026 at 18: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 Jun 24, 2026 at 08:16 UTC.

Stored context lists registrar Fewmoretaps OU d/b/a Trustname.com, IP address 2a06:98c1:3121::3, registration date Jun 12, 2026, apparent target Cryptoscam. 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.