Stored evidence for trezorsecure.io: VirusTotal recorded 11 detections among 89 scanners on 2026-09-08. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for trezorsecure.io. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 11 detections among 89 scanners in the stored snapshot dated 2026-09-08. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-08 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
Source Context
MetaMask and SEAL are recorded as named external blocklist observations for trezorsecure.io in the snapshot dated 2026-09-08. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains trezorsecure.io as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
Reachability and Timeline
The record first observed trezorsecure.io on 2026-09-08. The MetaMask and SEAL blocklist snapshot is dated 2026-09-08 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-08-31. A URLScan reference was stored on 2026-09-08 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
Registration and Infrastructure
The source stores 192.142.55.227 as the observed address in this record. The registration date for trezorsecure.io is recorded as 2026-08-31. The SSL issuer is recorded as Let's Encrypt / YR1 in the snapshot dated 2026-09-08. The stored ASN observation records 214036 and Ultahost, Inc. in this record. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
Conclusion
The trezorsecure.io record states that VirusTotal recorded 11 detections among 89 scanners on 2026-09-08. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-08. PhishDestroy remains a separate publisher catalogue entry in the stored record. The observed address field in this record contains 192.142.55.227. The supported conclusion is bounded to the exact stored observations for trezorsecure.io. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to trezorsecure.io during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain trezorsecure.io as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to trezorsecure.io. The stored record does not justify extending that rule to 192.142.55.227 or to other infrastructure records.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='trezorsecure.io', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
DOM Analysisanalyzed 2026年9月8日score 90/1002 brand signals
Submitted URLhttp://trezorsecure.io/
Favicon Hash
页面标题
Can’t Find the Server
Impersonates
GoogleTrezor
TLS 证书
Certificate hostname mismatch·
颁发者 Let's Encrypt· stored validity ends in 82 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
192.142.55.227
Network ASN
AS214036
Organization
Ultahost Inc
Observed location
Amsterdam, NL
Server header
Apache
域名服务器 4
dns1.hosted-domains.net
dns2.hosted-domains.net
dns3.hosted-domains.net
dns4.hosted-domains.net
Location describes the IP network.
TLS 证书
Issuer
Let's Encrypt
Valid from
2026-08-31 20:06:48
Valid until
2026-11-29 20:06:47
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-08 10:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprint93e18ee8dd8468d6f9508474773ab02008717c9e2a580ea32d0537063ecade4cCertificate names · 1 SANs
www.trezorsecure.io
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 01:29:13 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-17 22:35:54 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-17 22:35:54 UTC → 2026-09-30 16:14:55 UTC · 305.65hmidpoint estimate ≈ 2026-09-24 07:25:24 UTC · precision low · basis bounded
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.
技术 · 1 identified
A
Apache HTTP Server
Web servers
Apache is a free and open-source cross-platform web server software.
Last analyzed First positive detection Previous stored snapshot: 11 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
Lionic
SafeToOpen
SOCRadar
Sophos
网站性能分析
Google PageSpeed Insights — mobile performance audit of trezorsecure.io· checked Sep 8, 2026
100
Good
Performance
FCP
0.79s
First Contentful Paint
LCP
0.79s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.79s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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.
Domain Status Transition2026-09-18 10:35:32 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-08 10:01:38 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 192.142.55.227.
威胁响应 Pipeline
发现
Analysis
Monitoring
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
On the evening of 3 September 2026 and into the early hours of 4 September 2026, I was the victim of a prolonged and coordinated cryptocurrency fraud involving impersonation of the Metropolitan Police, Trezor and Cake Wallet.
The fraud began at approximately 8:04 p.m. with a t
1 report filed for trezorsecure.io (1 written by a person) · category: Impersonation · source checked
“On the evening of 3 September 2026 and into the early hours of 4 September 2026, I was the victim of a prolonged and coordinated cryptocurrency fraud involving impersonation of the Metropolitan Police, Trezor and Cake Wallet.
The fraud began at approximately 8:04 p.m. with a telephone call from an individual claiming to be a Metropolitan Police officer, lasting approximately 19 minutes. A second call from the same number began at approximately 8:24 p.m. and lasted approximately 1 hour 25 minu”
— reported by Anonymous on Sep 11, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
