fadex[.]cc

PhishDestroy first recorded fadex.cc on Jun 18, 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” on Aug 4, 2026 at 10:21 UTC. No conclusive HTTP response is stored, so current availability remains unverified.

VirusTotal returned 14 detections from 91 scanners in the stored check on Jul 8, 2026 at 22:20 UTC. The independent blocklist snapshot recorded 0 matches across 10 configured external sources on Aug 4, 2026 at 10: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 Jun 18, 2026 at 14:40 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 0 pulse references on Jun 18, 2026 at 15:20 UTC. OTX pulses are community-intelligence references, not vendor verdicts. Spamhaus DBL stored the result DBL_SPAM on Jul 18, 2026 at 18:30 UTC. A URLScan capture is stored from Jun 25, 2026 at 08:19 UTC.

Stored context lists registrar Cloud DNS Ltd, IP address 138.226.237.224, registration date Mar 26, 2026, apparent target Ethereum. 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.