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

reach-trezor.io

“Sign in”

注册商
OwnRegistrar
Resolved IP
188.114.97.3
Registered
2026年10月4日
威胁判定 高
可用性 最后已知的活跃状态 最新存储的可达性观察
风险信号
Spamhaus DBL: DBL_PHISH 存储的阻止列表匹配项：2 品牌冒充：Trezor 年轻域名：6 天龄
OTX: 1 ref 2026年10月11日 Trezor CDN
API
该域名已被标记为恶意域名
报告匹配的公共黑名单：2。 请格外小心——不要输入凭据或个人信息。
报告概览

reach-trezor.io — 最后已知的活跃状态 (HTTP 200). 品牌冒充：Trezor; 诈骗类型：Impersonation. 证据摘要: URLScan capture; Spamhaus DBL_PHISH; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 66/100. 注册商: OwnRegistrar.

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

Spamhaus DBL
DBL_PHISH
OTX references
1 community ref
URLScan
URLScan
报告 ↗
TLS 证书
已过期或未验证
年龄
6d Brand New!
观测状态
最后已知的活跃状态 200
PhishDestroy
DestroyList
已列入

Source evidence

4 sources

Spamhaus DBL

DBL_PHISH

OTX

1 community reference

报告

URLScan capture

存储的报告

Stored URLScan capture preview
报告

Google Safe Browsing

Checked; no threat flag recorded

报告

证据摘要

高
OTX
1 community ref
URLScan
Stored capture

Assessment

The domain reach-trezor.io returned an HTTP status 200 on 2026-10-11, providing a dated technical record of a successful HTTP status observation. On the same date, the domain was listed on two external blocklists, which is a notable recorded indicator from multiple sources.

Recorded Evidence

On 2026-10-11, reach-trezor.io was included on the MetaMask and SEAL external blocklists. The HTTP status record for this domain on 2026-10-11 was 200. OTX documented reach-trezor.io in one pulse as of 2026-10-11. The domain was registered with OwnRegistrar, Inc. on 2026-10-04, and its SSL certificate was issued by Let's Encrypt / YE2.

Interpretation

The PhishDestroy internal listing contains a record of reach-trezor.io, documenting its presence in a security intelligence source. The HTTP status observation provides a technical measurement of the domain's web response on a specific date. The external blocklist entries and the OTX pulse reference show that reach-trezor.io was noted by several security sources, each using its own criteria for listing.

Recommended Actions

Preserve the MetaMask and SEAL blocklist records for reach-trezor.io as reference points for future comparison. Retain the OTX pulse and PhishDestroy internal listing records for this domain to support ongoing review. Keep the HTTP status 200 record as a technical benchmark for past network response.

探测与规避分析

隐身和流量分配检查

尚未扫描 目前尚未记录到爬虫与浏览器之间的差异

针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。

存储的隐身标志
尚未扫描
上次隐形扫描
扫描器检测到的服务器头信息
cloudflare

扫描说明: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare

TDS指纹识别实时演示
七个Keitaro指纹，外加爬虫与浏览器的对比，当此面板打开时，由PhishDestroy扫描器运行。
等待

已保存的截图 · 2 captures

Primary capture 1 / 2
来源Primary capture
Recorded2026-10-11 09:55 UTC
StateStored capture
Position1 / 2
查看原图 Open raw image Wayback 下载

Domain details

域名
IP Context Cloudflare shared edge origin IP hidden Edge-IP 声誉不属于此域。
OTX Tags blocklistcryptodrainerfraudphishdestroyphishingscam
注册商 OwnRegistrar US(US)
ICANN 注册管理机构ICANN Lookup (RDAP) →
WHOIS查询reach-trezor.io 的 ICANN RDAP →
注册信息创建 2026年10月4日 (6d · Brand New!) — Expires 2027年10月4日
HTTP 状态码200
技术详情Provenance & timestamps
首次发现2026年10月11日
DOM Analysisanalyzed 2026年10月11日score 0/100
Submitted URLhttp://reach-trezor.io/
Favicon Hash
页面标题
Sign in
TLS 证书
Hostname coverage not recorded · 颁发者 Let's Encrypt / YE2 · stored validity ends in 84 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP 声誉不属于此域。

域名服务器 2

  • adelaide.ns.cloudflare.com
  • junade.ns.cloudflare.com

Location describes the IP network.

TLS 证书

Issuer
Let's Encrypt / YE2
Valid from
2026-10-05 18:51:41
Valid until
2027-01-03 18:51:40
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-11 10:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint0435094a401754405fa23d92a71991e96b5210e1feb86d22b6af552600c6bcc4

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

viewdns.info · 188.114.97.3rapiddns.io

Latest Classified Outcome 2026-10-11 11:02:13 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-11 11:02:13 UTC
RDAP registration 未知
Observed timeline last reachable: 2026-10-11 11:02:13 UTC last content: 2026-10-11 11:02:13 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.
举报此域名 提交证据，帮助保护他人

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Threat First Observed 2026-10-11 09:55:41 UTC
    Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.97.3.

威胁响应 Pipeline

发现
Analysis
Monitoring

9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

已捕获威胁
reach-trezor.io 已检测到并排入队，待进行全面分析
2026年10月11日
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
2026年10月11日
URLScan.io Capture
已存储 URLScan report with capture artifacts
2026年10月11日
黑名单检测
见于 2 blocklists: MetaMask, SEAL
2026年10月11日
OTX Community References
1 community publication reference on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月11日
Brand Impersonation
Impersonation of Trezor
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
2026年10月11日
Technical Analysis Recorded
该报告包含存储的技术或取证分析结果。
2026年10月11日
DestroyList 已发布
Listed in the public PhishDestroy/DestroyList repository
2026年10月11日
Monitoring Continues
该域仍然可达或访问受限；未来的检查可能会更新这一观察结果。
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web Symantec网站评审 AviraURL reporting Avast / AVGURL reporting 卡巴斯基OpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

公共封禁名单状态

仿冒域名

已存储 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

证据与外部报告

证券分析
URLScan Stored capture VirusTotal ChainPatrol URLQuery SSL 实验室 Hostname coverage not recorded 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
DNS 与网络
nslookup.io DNS bgp.tools ASN /路线
SEO 与域名
SpyFu Moz DA/PA Ahrefs 反向链接
深度分析
深度分析

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

4 evidence signal groups linked 0 reports recorded 最后已知的活跃状态
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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

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

向当地主管部门报告

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

97个国家目录

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

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

检查任意域名

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

立即扫描

举报网络钓鱼

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

报告

实时威胁动态

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

监控

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

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

实时威胁动态 对该列表提出异议
HTML · IFRAME

嵌入此报告

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

embed.html 
<iframe
  src="https://phishdestroy.io/zh/embed/domain/reach-trezor.io"
  title="PhishDestroy threat report for reach-trezor.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>