managetrezor[.]app

PhishDestroy first observed managetrezor.app on Aug 16, 2026. The hostname explicitly references Trezor; stored content metadata identifies the same apparent target. Current evidence score: 80/100 (critical).

Positive findings are stored from 3 sources: VirusTotal, Spamhaus DBL, and Cloudflare Radar. VirusTotal recorded 6 detections among 91 engines: CRDF, Emsisoft, Fortinet, Kaspersky, Netcraft, PhishFort on Aug 16, 2026 at 05:34 UTC. Spamhaus DBL: DBL_PHISH on Aug 16, 2026 at 06:30 UTC. Cloudflare Radar classified the hostname as malicious and placed it in the phishing category; its verdict timestamp was not retained. Non-positive and contextual checks: AlienVault OTX listed 2 community pulse references (not vendor detections) on Aug 16, 2026 at 05:35 UTC. The separate external-blocklist snapshot contained no matches on Aug 16, 2026 at 06:20 UTC. Google Safe Browsing returned no flag on Aug 16, 2026 at 05:34 UTC.

HTTP 301 was recorded on Aug 16, 2026 at 05:28 UTC. TLS metadata lists Let's Encrypt as the certificate issuer.

Neither a page title nor a landing-page capture is stored. The content indicators and 3 positive source findings support the current Trezor impersonation and phishing classification. The target field identifies Trezor, but the record does not establish whether the page requested credentials, a seed phrase, or a wallet connection.