trezor[.]rest

PhishDestroy first observed trezor.rest on Aug 19, 2026. The hostname explicitly references Trezor; stored content metadata identifies the same apparent target. The captured page title is “TREZOR”. Current evidence score: 58/100 (high).

Positive findings are stored from 2 sources: SEAL and URLScan. SEAL listed the hostname in the separate external-blocklist snapshot on Aug 19, 2026 at 22:20 UTC. URLScan returned a malicious verdict with score 100; scan metadata linked the capture to Trezor and Investmentscam and assigned phishing as its category on Aug 19, 2026 at 23:08 UTC. Non-positive and contextual checks: On Aug 19, 2026 at 23:28 UTC, VirusTotal recorded 0 detections among 91 engines; Google Safe Browsing returned no flag. URLQuery recorded no positive detection; no observation timestamp was retained. The 0/91 VirusTotal snapshot and the positive findings above are conflicting observations from different sources or collection times.

The collector marked the hostname reachable on Aug 19, 2026 at 22:57 UTC, but did not retain the HTTP response code. Registration records for the domain list Gname.com Pte. Ltd. as the registrar and Aug 18, 2026 as the creation date. Registration preceded first observation by 1 day. At collection time, the hostname resolved to 104.21.85.22. The IP and ASN identify shared Cloudflare edge infrastructure; the origin server is not established by this address. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. TLS metadata lists Google Trust Services as the certificate issuer.

The content indicators and 2 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.