VirusTotal
9 / 91 engine detections
Open reportnot-start-eng-trezr.pages.dev is a Trezor impersonation page detected by PhishDestroy on 2026-09-15. Risk: critical (83/100). Registrar: CloudFlare. Status: Reachable · access restricted. Hosting: Cloudflare, Inc. VirusTotal: 9/91 engines flag it. Do not enter credentials or connect a wallet.
“Trezor Device Setup - Unique Interface”
9 / 91 engine detections
Open reportno community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
not-start-eng-trezr.pages.dev is a phishing page impersonating Trezor, the hardware wallet maker. It targets Trezor owners who go looking for setup help. The page presented itself as "Trezor Device Setup - Unique Interface", and the misspelled "trezr" in the address is meant to pass a quick glance. PhishDestroy first saw it on 2026-09-15. It has been offline since 2026-09-27, and the hosting provider has blocked its content, which was still the case at the last check on 2026-10-19.
Fake Trezor setup pages copy the look of the official onboarding flow. They tell the visitor that the device needs to be initialized, restored or verified. At the critical step, the page asks for the 12- or 24-word recovery phrase, which a genuine Trezor never asks you to type into a website. Anyone who submits those words gives the attackers full control of the wallet. They can sweep every asset tied to it from anywhere, and the hardware device offers no protection.
On 2026-09-27, VirusTotal showed 9 of 91 security engines flagging the domain. The vendors included Kaspersky, Sophos, Fortinet, Forcepoint ThreatSeeker, G-Data, alphaMountain.ai, LevelBlue and the phishing feed OpenPhish. Beyond PhishDestroy, the domain sits on the MetaMask and SEAL blocklists, which are both curated specifically for crypto threats. Agreement between those wallet-focused lists and the general security vendors supports the impersonation verdict.
The site ran on Cloudflare's free pages.dev hosting, served through Cloudflare, Inc. with a Canadian location. Throwaway subdomains like this one cost nothing to create and borrow the reputation of a trusted platform. The registration date of 2026-08-02 falls about six weeks before PhishDestroy first detected the page.
If you typed your recovery phrase into this page, treat the wallet as compromised. Set up a new wallet with a fresh phrase, preferably by resetting your Trezor through the official Trezor Suite. Then move any remaining funds to it immediately. Revoke token approvals granted from the exposed addresses, and never reuse the leaked phrase. Defenders should block the domain and watch for lookalike pages.dev subdomains that combine Trezor with setup or language keywords.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 6c3a9477-f9e9-4997-8b8c-a924eccd458c |
|---|---|
| Final url | https://not-start-eng-trezr.pages.dev/ |
| Status | 200 |
| History | [
{
"url": "https://not-start-eng-trezr.pages.dev/",
"status": 200
}
] |
| DOM structure hash | 55f41842dc43fd670806c1c4c0c30169b00521fb98db55b692ec76eaf537ec54 |
| Document hash | 04c0f40e382817d5eff46899d2661833d486a3d0ea6cdddb32e2c9604ac718af |
| Phishing v2 | [
"phishing"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "not-start-eng-trezr.pages.dev",
"type": "A",
"value": "188.114.97.0"
},
{
"name": "not-start-eng-trezr.pages.dev",
"type": "A",
"value": "188.114.96.0"
},
{
"name": "not-start-eng-trezr.pages.dev",
"type": "AAAA",
"value": "2a06:98c1:3121::"
},
{
"name": "not-start-eng-trezr.pages.dev",
"type": "AAAA",
"value": "2a06:98c1:3120::"
}
] |
| Dnssec valid | false |
| Ip | 188.114.97.0 |
| Registration record | {
"registrar": "CloudFlare, Inc.",
"created": "2020-09-02T02:33:29Z",
"updated": "2026-06-09T12:00:52Z",
"expires": "2027-09-02T02:33:29Z",
"nameservers": [
"adi.ns.cloudflare.com",
"karl.ns.cloudflare.com"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 56,
"malicious": 0,
"suspicious": 0,
"undetected": 36
} |
|---|---|
| Reputation | 0 |
| Registrar | CloudFlare, Inc. |
| Created | 2020-09-02T02:33:29Z |
| Expires | 2026-09-02T02:33:29Z |
| Updated | 2025-03-17T14:56:22Z |
| First seen | 2025-10-10T06:47:38Z |
| DNS records | [
{
"ttl": 21600,
"type": "NS",
"value": "curt.ns.cloudflare.com"
},
{
"ttl": 1800,
"type": "SOA",
"rname": "dns.cloudflare.com",
"value": "curt.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "A",
"value": "172.66.44.163"
},
{
"ttl": 21600,
"type": "NS",
"value": "delilah.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:310c::ac42:2ca3"
},
{
"ttl": 300,
"type": "A",
"value": "172.66.47.93"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:310c::ac42:2f5d"
}
] |
| Dns at | 2026-10-19T22:28:15Z |
| Jarm | 27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6 |
| Certificate | {
"san": [
"not-start-eng-trezr.pages.dev",
"*.not-start-eng-trezr.pages.dev"
],
"issuer": "Google Trust Services / WE1",
"serial": "47633c5720d1f0c40e3266b92ed63cf9",
"sha256": "c0eba1eb4ebb2d42f3c171225c9c42327e20fa60fe4728ad58632bdb5fb8e88c",
"subject": "not-start-eng-trezr.pages.dev",
"valid_to": "2026-12-29T09:00:06Z",
"valid_from": "2026-09-30T08:00:12Z"
} |
| Registration record | {
"registrar": "CloudFlare, Inc.",
"registrar_iana_id": "1910",
"registrar_url": "None",
"created": "2020-09-02T02:33:29Z",
"updated": "2023-09-04T18:15:07Z",
"expires": "2026-09-02T02:33:29Z",
"status": [
"clientDeleteProhibited",
"clientTransferProhibited",
"clientUpdateProhibited",
"clientdeleteprohibited",
"clienttransferprohibited",
"clientupdateprohibited"
],
"nameservers": [
"adi.ns.cloudflare.com",
"karl.ns.cloudflare.com"
],
"dnssec": "unsigned"
} |
No. PhishDestroy classifies not-start-eng-trezr.pages.dev as a Trezor impersonation page (risk: critical, 83/100); it was first detected on 2026-09-15. VirusTotal: 9/91 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on not-start-eng-trezr.pages.dev. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
Last checked
Edge-IP reputation is not attributed to this domain.
adi.ns.cloudflare.comkarl.ns.cloudflare.comLocation describes the IP network.
de3d2a099c6865f4195e61289c31f4c40872035ce1cf4a269171e4954bb7011enot-start-eng-trezr.pages.dev*.not-start-eng-trezr.pages.devSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of not-start-eng-trezr.pages.dev · checked Sep 22, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
not-start-eng-trezr.pages.dev
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Reachable→Unavailable
Reachable
9/91 engine detections
View sourceNo threat flag
View sourcenot-start-eng-trezr.pages.dev
View source74 stored lookalike domains
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
not-start-eng-trezr.pages.dev)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.