VirusTotal
16 / 92 engine detections
レポートを開く“500: Internal Server Error”
MetaMaskなりすまし: start-faq-en-trezr--public.typedream.app — 最後に確認されたアクティブな状態 (HTTP 301). 証拠の概要: VirusTotal 16/92 (ChainPatrol, alphaMountain.ai, BitDefender…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
16 / 92 engine detections
レポートを開くno community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This hostname sits on the typedream.app site-building platform and uses a misspelled "trezr" plus "start" and "faq" to pass as an official Trezor setup or help page. It targets Trezor hardware wallet owners. PhishDestroy first flagged it on 2026-10-03 and classifies it as an impersonation phishing page. As of 2026-10-19 the site was still alive and responding with a redirect. Its page title reads "500: Internal Server Error", while our classification is impersonation phishing.
Fake Trezor "start" and FAQ pages usually copy the onboarding flow and tell visitors their device needs setup, a firmware fix or a wallet check. The goal is to get the victim to type their 12- or 24-word recovery seed into a web form. Anyone holding that seed can rebuild the wallet on their own device and empty it. The hardware wallet's protection does not help once the seed is out. Trezor never asks for a recovery seed on a website.
On 2026-10-09, 16 of 92 VirusTotal engines flagged the hostname. The vendors included ChainPatrol, alphaMountain.ai, BitDefender, ESET, Emsisoft, Fortinet, G-Data and Gridinsoft. That mix of a crypto-focused scanner and several mainstream antivirus vendors points to independent confirmation, not a single source. The site is also listed on the MetaMask and SEAL blocklists alongside PhishDestroy, so wallet users with those protections should see a warning.
The page is a subdomain on a shared website builder, so it carries the builder's domain rather than a freshly registered one. Traffic routes through Cloudflare (AS13335, IP 188.114.96.1, US), which masks the origin server. The Google Trust Services certificate is issued automatically, so the browser padlock says nothing about whether the page is legitimate.
If you typed your recovery seed into this site, treat the wallet as compromised. Set up your genuine Trezor with a brand-new seed, then move all funds to it at once, before the attacker does. If you only browsed and entered nothing, close the page and reach Trezor solely through addresses you have bookmarked yourself. Defenders should block the full hostname and report it to the typedream.app platform and Cloudflare for takedown. They should also watch for similar misspelled Trezor subdomains on site-builder services.
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
138556077c63e0419543a8da6c8303688b66bb0ab78ce09b1973983fa45d16a4typedream.appSaved 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 start-faq-en-trezr--public.typedream.app · checked Oct 3, 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.
redirect: raw=redirect_301; http=301; via=http_proxy; location=https://start-faq-en-trezr--public.typedream.app/; server=cloudflare
start-faq-en-trezr--public.typedream.app
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
利用不可→到達可能
不明→inactive
http_no_content
不明→inactive
http_no_content
到達可能→利用不可
No threat flag
View source16/92 engine detections
View sourcestart-faq-en-trezr--public.typedream.app
View source保存された類似ドメイン:79 件
コミュニティ報告:1 件
カテゴリIMPERSONATION
Brand abuse: copyrighted content, fake affiliation, fenced impersonation, impersonation, impersonating Trezor
Listed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
start-faq-en-trezr--public.typedream.app)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.