zeazax[.]com

PhishDestroy first recorded zeazax.com on Jul 20, 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 100/100.

The latest stored availability state is “Last known active” (HTTP 200) on Aug 5, 2026 at 10:50 UTC. This is a reachability snapshot, not proof of the cause of any outage, restriction, or status change.

VirusTotal returned 16 detections from 91 scanners in the stored check on Jul 30, 2026 at 02:18 UTC. The independent blocklist snapshot recorded 2 matches (MetaMask, SEAL) across 10 configured external sources on Aug 5, 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 Jul 20, 2026 at 15:45 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 0 pulse references on Jul 20, 2026 at 15:46 UTC. OTX pulses are community-intelligence references, not vendor verdicts. The Spamhaus DBL snapshot stored no positive result on Jul 20, 2026 at 18:30 UTC. That result is not evidence of safety. A URLScan capture is stored from Jul 20, 2026 at 15:44 UTC.

Stored context lists registrar Fewmoretaps OU d/b/a Trustname.com, IP address 172.67.218.247, registration date Jul 15, 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.