fuz[.]za[.]com

PhishDestroy first recorded fuz.za.com on Jul 30, 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 95/100.

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

VirusTotal returned 10 detections from 91 scanners in the stored check on Aug 2, 2026 at 02:01 UTC. The independent blocklist snapshot recorded 0 matches across 10 configured external sources on Aug 4, 2026 at 18:20 UTC. PhishDestroy's own listing is excluded from that count. A zero-match snapshot is not a safety verdict.

Other stored evidence. Google Safe Browsing stored no positive flag on Jul 30, 2026 at 12:24 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 0 pulse references on Jul 30, 2026 at 12:25 UTC. OTX pulses are community-intelligence references, not vendor verdicts. Spamhaus DBL stored the result DBL_SPAM on Jul 30, 2026 at 14:30 UTC. A URLScan capture is stored from Jul 30, 2026 at 12:22 UTC.

Stored context lists IP address 102.220.160.24, apparent target ["microsoft"]. 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.