trxweb3[.]org

PhishDestroy first recorded trxweb3.org on Jun 15, 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 5, 2026 at 02:07 UTC. No conclusive HTTP response is stored, so current availability remains unverified.

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

Other stored evidence. Google Safe Browsing stored no positive flag on May 28, 2026 at 05:00 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 1 pulse reference on May 28, 2026 at 05:14 UTC. OTX pulses are community-intelligence references, not vendor verdicts. The Spamhaus DBL snapshot stored no positive result on Jul 13, 2026 at 14:34 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.

Stored context lists registrar July Name Limited, IP address 134.122.140.79, registration date May 27, 2026, apparent target MetaMask. 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.