VirusTotal
19 / 91 engine detections
レポートを開く“Trezor Hardware Wallet (Official) | Bitcoin & Crypto Security | Trezor”
Trezorなりすまし: trezor.center — コンテンツが利用できません (HTTP 451). 証拠の概要: VirusTotal 19/91 (ChainPatrol, alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF); URLScan…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
19 / 91 engine detections
レポートを開く悪意あり
レポートを開くchecked — no detections recorded
レポートを開く17 community references
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The domain trezor.center impersonates the cryptocurrency hardware wallet brand Trezor. Despite being offline, it represents a sophisticated attempt to deceive users. The domain was registered with Name.com, Inc. and hosted on an IP address managed by Amazon.com, Inc. (AS16509) in the US. It was issued an SSL certificate by Let's Encrypt, indicating a level of technical competence in setting up the scam site.
PhishDestroy detected trezor.center on June 21, 2026, just one day after its creation. At the time of detection, the domain had 0 hits on VirusTotal, highlighting its freshness and the rapid response of PhishDestroy's detection pipeline. This early detection is crucial as it exploits the typical 24-72 hour window before AV databases update their records. The domain's presence on public blocklists from PhishDestroy, MetaMask, and SEAL further underscores its malicious intent.
The platform risk score for trezor.center is 85 out of 100, indicating a high threat level. This score reflects factors such as the impersonation of a well-known brand and the technical setup of the phishing site. Although the site is currently offline, its initial setup and rapid detection illustrate the ongoing risk posed by similar phishing attempts. Users should remain aware of such threats and verify the authenticity of websites before entering sensitive information.
Last checked
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Edge-IP の評判はこのドメインに起因しません。
ns1.vercel-dns.comns2.vercel-dns.comLocation describes the IP network.
743be35abdbcb92fc636645ca9fa4d6b8f82a2ac97961c37f6718596c3c3a0ccSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
content_split · dead_http: raw=http_451; http=451; via=https_proxy; server=Vercel; provider_error=DEPLOYMENT_DISABLED
trezor.center
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→blocked
vercel_deployment_disabled · Vercel · deployment_disabled
不明→blocked
vercel_deployment_disabled · Vercel · deployment_disabled
不明→blocked
vercel_deployment_disabled · Vercel · deployment_disabled
不明→blocked
vercel_deployment_disabled · Vercel · deployment_disabled
到達可能→利用不可
不明→protected
http_access_restricted · access_restriction
利用不可→到達可能
不明→blocked
vercel_deployment_disabled · Vercel · deployment_disabled
不明→blocked
vercel_deployment_disabled · Vercel · deployment_disabled
不明→blocked
vercel_deployment_disabled · Vercel · deployment_disabled
不明→blocked
vercel_deployment_disabled · Vercel · deployment_disabled
不明→blocked
vercel_deployment_disabled · Vercel · deployment_disabled
到達可能→利用不可
17 community references
View source19/91 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcePD-20260621-F9EA2F
trezor.center
View source保存された類似ドメイン:74 件
PD-20260621-F9EA2F Recipient: abuse@name.com アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
trezor.center)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.