跳转到安全报告
分析仪表盘
域安全和威胁情报
trezorcheckup.io favicon

trezorcheckup.io

“trezorcheckup.io”

注册商
NETIM SAS
Resolved IP
172.67.198.16
Registered
2026年10月17日
PhishDestroy assessment 关键
可用性 最后已知的活跃状态 最新存储的可达性观察 观察到 · HTTP probe
风险信号
病毒检测总数：2/92 存储的阻止列表匹配项：2 自动品牌标签：Trezor 年轻域名：3 天龄
OTX: 1 ref 2026年10月20日 CDN
API
该域名已被标记为恶意域名
安全引擎报告检测：2。 报告匹配的公共黑名单：2。 请格外小心——不要输入凭据或个人信息。
VirusTotal
2 / 92
engine detections
Google Safe Browsing
No threat flag
OTX
1
community references
Page captures
2
open gallery
Domain age
3 days
报告概览

冒充 Trezor: trezorcheckup.io — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 2/92 (Gridinsoft, SOCRadar); 2 external blocklist matches (MetaMask, SEAL); PhishDestroy…

为保留原始取证记录，下方的 PhishDestroy AI 详细分析仍使用英文。

Source evidenceVirusTotal 2 / 92 · OTX 1 references 5 sources

VirusTotal

2 / 92 engine detections

打开报告

Google Safe Browsing

No threat flag

打开报告

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

关键
VirusTotal
2 / 92
OTX
1 community ref
Page captures
2
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy has listed trezorcheckup.io as a suspicious domain. The recorded page title is “trezorcheckup.io”. The domain was first observed by PhishDestroy on 2026-10-20.

How the scam works

Because the domain is flagged without a concrete category, the exact malicious behavior cannot be determined. Typical risks for suspicious domains include phishing, malware delivery, or fraudulent services, but none have been observed on this site.

Evidence

VirusTotal reported 2 detections out of 92 engines, with Gridinsoft and SOCRadar flagging the site; the results were retrieved on 2026-10-20 after analysis on 2026-10-19. Google Safe Browsing showed no flag as of 2026-10-20. External blocklists MetaMask and SEAL both listed the domain (2 total) on 2026-10-20, and PhishDestroy’s internal list also includes it as of that date. OTX recorded one pulse referencing the domain on 2026-10-20.

Infrastructure

The recorded IP address for trezorcheckup.io is 172.67.198.16.

What to do

If you only visited the site, no immediate action is required. If you entered any credentials, change the associated passwords and monitor the accounts for unusual activity. Defenders should add a rule to block or monitor traffic to trezorcheckup.io and review any logs that show connections to the recorded IP.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask 已列入 View source
PhishDestroy PhishDestroy list View source
SEAL 已列入 View source

Last checked

已保存的截图 · 2 captures

Primary capture 1 / 2
来源Primary capture
Recorded2026-10-20 13:11 UTC
StateStored capture
HTTP status at archiveHTTP 200
Final URLhttps://trezorcheckup.io/
Position1 / 2
Open capture Wayback 下载

Domain details

域名
URLScan verdict 分析完成 score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP 声誉不属于此域。
OTX tags blocklistcryptodrainerfraudphishdestroyphishingscam
注册商 NETIM SAS
ICANN 注册管理机构ICANN Lookup (RDAP) →
WHOIS查询trezorcheckup.io 的 ICANN RDAP →
注册信息创建 2026年10月17日 (3d · Brand New!) — Expires 2027年10月17日
HTTP 状态码200
技术详情Provenance & timestamps
首次发现2026年10月20日
DOM Analysisanalyzed 2026年10月20日score 83/1001 brand signal
Submitted URLhttp://trezorcheckup.io/
Favicon Hash
Observed page title
trezorcheckup.io
Automated brand references
Trezor
TLS 证书
颁发者 Let's Encrypt / YE1 · stored validity ends in 86 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.67.198.16
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

Edge-IP 声誉不属于此域。

域名服务器 2

  • ingrid.ns.cloudflare.com
  • ezra.ns.cloudflare.com

Mail routing 2 MX records

  • mx2.netim.netpriority 10
  • mx1.netim.netpriority 10

Location describes the IP network.

TLS 证书

Issuer
Let's Encrypt / YE1
Valid from
2026-10-17 23:18:24
Valid until
2027-01-15 23:18:23
Validity
Within stored validity dates
Collection time
2026-10-20 22:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprintdc83b63ef1216971c27318714b21ca9b8192a287d96b8b2656b5011e8d7f71bb

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 172.67.198.16rapiddns.io

Latest Classified Outcome 2026-10-21 01:58:15 UTC

Primary outcome 内容在线 reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation 内容在线 Ordinary HTTP content served 90% 2026-10-21 01:58:15 UTC
RDAP registration 未知
Observed timeline last reachable: 2026-10-21 01:58:15 UTC last content: 2026-10-21 01:58:15 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
技术 · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据，帮助保护他人

VirusTotal 分析

2 / 92 安全供应商标记了该域
View on VT
Last analyzed Previous stored snapshot: 2 detections
Gridinsoft
SOCRadar

存档证据

Wayback Machine Snapshot
历史快照可供证据审查
View Archive
网站性能分析

Google PageSpeed Insights — mobile performance audit of trezorcheckup.io · checked Oct 20, 2026

99
Good
Performance
FCP
1.62s
First Contentful Paint
LCP
1.62s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
19ms
Total Blocking Time
SI
1.62s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://trezorcheckup.io/
Final URL: https://trezorcheckup.io/
trezorcheckup.io
响应
HTTP 200
HTML body
4.9 KB
Compressed
1.5 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
Server: cloudflare
X-Powered-By: PHP/8.5.4
Cache-Control: no-store, no-cache, must-revalidate
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 15
alt-svc
h3=":443"; ma=86400
Cache-Control
no-store, no-cache, must-revalidate
cf-cache-status
DYNAMIC
CF-RAY
a4d84ba369fecef6-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Tue, 20 Oct 2026 13:16:10 GMT
Host
trezorcheckup.io
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=Y5SYZ2xEi3PTZhxM9y7kS8ri0%2Bla6VwlN75UMSPYT8cubL58hjMLMV2HM8RWrYHVIzKk1tDCVYp5bOelZ4YIIk03As2KtLCAb6cge%2BEb%2FWuMviUwIAJJlGCVPhpHudHePcXY"}]}
Server
cloudflare
Transfer-Encoding
chunked
Vary
accept-encoding
X-Powered-By
PHP/8.5.4

Values retained by the collector; long values may be shortened during collection.

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history1

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    未知→live_content

    content_served

Recorded activity

4 entries
  1. AlienVault OTX

    1 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    2/92 engine detections

    View source
  4. Added to PhishDestroy

    trezorcheckup.io

    View source

仿冒域名

已存储 74 个仿冒域名

treaor.io replacement 内部报告 treozr.io transposition 内部报告 trzezor.io insertion 内部报告 trzor.io omission 内部报告 rtrezor.io insertion 内部报告 terezor.io insertion 内部报告 trazor.io bitsquatting 内部报告 trexzor.io insertion 内部报告 trezort.io addition 内部报告 5rezor.io replacement 6rezor.io replacement frezor.io replacement
显示全部（62）
grezor.io replacement rezor.io omission rrezor.io replacement rtezor.io transposition tdezor.io replacement teezor.io replacement terzor.io transposition tezor.io omission tfezor.io replacement tr.ezor.io subdomain tr3zor.io replacement treeor.io replacement treezor.io insertion treor.io omission treqor.io replacement tresor.io replacement trezeor.io insertion trezer.io vowel-swap trezior.io insertion trezir.io replacement trezkor.io insertion trezlor.io insertion trezo.io omission trezoe.io replacement trezoir.io insertion trezopr.io insertion trezor-io.com various trezorio.com various trezot.io replacement trezpor.io insertion trezpr.io replacement trezr.io omission trezro.io transposition trezxor.io insertion trezzor.io insertion trizor.io vowel-swap trozor.io vowel-swap trrzor.io replacement trtezor.io insertion trwezor.io insertion trwzor.io replacement trzeor.io transposition trzzor.io replacement ttezor.io replacement ttrezor.io insertion tyrezor.io insertion yrezor.io replacement ytrezor.io insertion prezor.io bitsquatting treazor.io insertion trerzor.io insertion trewzor.io insertion trexor.io bitsquatting trez0r.io homoglyph trezaor.io insertion trezora.io addition trezore.io addition trezoro.io addition trezorr.io addition trezors.io addition xn--tezor-5bb.io homoglyph xn--trezo-9bb.io homoglyph

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

trezorcheckup.io

证据与外部报告

证券分析
URLScan Analyzed VirusTotal 2 det. ChainPatrol URLQuery SSL 实验室 CF雷达 打开报告 OTX 1 ref WOT ScamAdviser 黑名单检查器 URLVoid Sucuri SiteCheck MDN 观测站
OSINT与情报分析
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox 哈德逊岩 Sign-in search IntelX crt.sh 证书 WHOIS Wayback Archived
DNS 与网络
nslookup.io DNS bgp.tools ASN /路线
SEO 与域名
SpyFu Moz DA/PA Ahrefs 反向链接
深度分析
深度分析
Help & reporting

您是否受到本网站的影响？

4 evidence signal groups linked 0 stored notification records 最后已知的活跃状态

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

如果您输入了帐户凭据、个人或付款信息，或者从此域下载了文件，请立即采取措施。以下资源可帮助您报告事件并保护自己。

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review 不是执法报告
域名申诉
如果您拥有该域名并认为该列表不正确，请请求审核
警惕“数据恢复”诈骗！ 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。

97个国家目录

Template-based draft · optional AI wording assistance requires separate consent

AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident

针对受害者的建议与指导

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.

  • 更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
  • 启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
  • 冻结卡片 如果您在钓鱼网站上输入了银行信息

我应该为报告收集哪些信息？

联邦调查局（FBI）指南

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • 确切日期和时间 — 每笔交易的详情以及与诈骗者的首次接触
  • 屏幕截图 — 诈骗网站、聊天消息、电子邮件、钱包交易、社交媒体
  • 所有网址和域名 诈骗者使用的（包括 trezorcheckup.io)
  • 通信 — 诈骗者使用的电子邮件、短信、电话号码、用户名

即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整，对调查仍有帮助。

我应该向哪里举报这起诈骗？

  • 联邦调查局（FBI）IC3 — 互联网犯罪投诉中心（美国联邦举报渠道）
  • 欧洲刑警组织 — 欧洲网络犯罪报告（欧盟）
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • 当地警方 — 即使无法立即采取行动，也能留下正式记录

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • 虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
  • 猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
  • 退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • 利用人工智能实施的诈骗 — 深度伪造、自动化网络钓鱼以及人工智能生成的网站，使得欺诈行为更难被察觉

将来我该如何保护自己？

  • 将官方网站添加到书签 — 切勿点击来自电子邮件、私信或广告中的链接
  • 验证域名 — 查看 PhishDestroy 在进行互动之前，请检查HTTPS、拼写和域名注册时间。
  • “好得令人难以置信”=骗局 — 保证收益、名人代言、紧迫的截止日期

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

检查任意域名

使用存储的阻止列表、WHOIS、DNS 和公共扫描证据进行威胁分析

立即扫描

举报网络钓鱼

将可疑域名提交至我们的威胁数据库——保护社区

报告

实时威胁动态

最近的网络钓鱼报告和观察到的可用性变化

监控

随时掌握最新信息，确保安全

请实时监控威胁，或者如果您认为这是误报，请对该条目提出异议

实时威胁动态 对该列表提出异议
About this reportSources, observation dates and corrections

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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

嵌入此报告

在您的网站或博客上分享此威胁情报

embed.html 
<iframe
  src="https://phishdestroy.io/zh/embed/domain/trezorcheckup.io"
  title="PhishDestroy threat report for trezorcheckup.io"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>