Skip to security report
Analytics Dashboard
Domain security and threat intelligence
trezorsecure.io favicon

trezorsecure.io

“Can’t Find the Server”

Threat verdict Critical 92/100 evidence score
Availability Content unavailable Content was unavailable in the latest observation
Risk signals
VirusTotal detections: 14/89 Stored blocklist matches: 2 Brand impersonation: Google Young domain: 19 days old
OTX: 4 refs Sep 8, 2026 Google
Actions API
⚠️
This domain has been flagged as malicious
Security engines reporting a detection: 14. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Report overview

Stored evidence for trezorsecure.io: VirusTotal recorded 11 detections among 89 scanners on 2026-09-08.

The detailed PhishDestroy AI analysis below remains in English to preserve the original forensic record.

Evidence Summary

CRITICAL
Score
92/100

Assessment
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.

VirusTotal
VirusTotal
14 det.
OTX references
4 community refs
URLScan
URLScan
Report ↗
TLS Certificate
Let's Encrypt
Age
19d Very New!
Observed status
Content unavailable
PhishDestroy
DestroyList
Listed
Data coverage VirusTotal 14 / 89 OTX 4 community references CF Radar scan completed URLScan capture stored report URLScan verdict Analysis completed TLS valid certificate, 82d WHOIS 19d old Screenshot 2 captures · 2 sources

Forensic History & Detection Timeline

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. Domain Status Transition Sep 18, 2026 · 12:35 UTC
    Domain state transitioned from alive to dead.
  2. Threat First Observed Sep 8, 2026 · 12:01 UTC
    Domain ingestion complete. Initial state is marked as alive pointing to IP 192.142.55.227.

Threat Response Pipeline

Discovery
Checks
Reports
Availability
15/16

Public Blocklist Status

Evasion analysis

Cloaking & traffic-distribution check

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan

Scanner note: dns_error: raw=dns_error; via=local_dns_prefilter

Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this section scrolls into view.
Waiting

Stored Capture · 2 sources

Primary capture 1 / 2
SourcePrimary capture
Captured2026-09-08 10:01 UTC
StateStored capture
Position1 / 2
View Full Size Open raw image Wayback Download

Domain Intelligence

Domain
URLScan Verdict Analysis completed score 0 report ↗
Server / ASN Apache · AS214036 Ultahost, Inc.
IP Reputation abuse score 0/100 0 reports checked Sep 8, 2026
OTX Tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Devexpanse
ICANN RegistryOfficial ICANN accredited-registrars →
WHOIS LookupICANN RDAP for trezorsecure.io →
IP Address 192.142.55.227 NL
GeoNL Amsterdam, NL
NetworkAS214036 · Ultahost Inc
Reverse IPviewdns.info → rapiddns.io →
RegistrationCreated Aug 31, 2026 (19d · Very New!) — Expires Aug 31, 2027
Time to First Unavailability 10 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsDNS, SSL SANs, timestamps
First DetectedSep 8, 2026
DOM Analysisanalyzed Sep 8, 2026score 0/1002 brand signals
IoC Extractionscanned Sep 9, 20260 wallet · 0 Telegram IoCs
Submitted URLhttp://trezorsecure.io/
Nameserversdns1.hosted-domains.netdns2.hosted-domains.netdns3.hosted-domains.netdns4.hosted-domains.net
TLS Fingerprint
TLS Observationvalid from Aug 31, 2026scanned Sep 8, 2026
TLS SAN Domainswww.trezorsecure.io
Favicon Hash
Page Title
Can’t Find the Server
Impersonates
Google Trezor
TLS Certificate
Valid transport encryption · Issued by Let's Encrypt · valid for 82 days
Technologies · 1 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

14 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 11 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
SafeToOpen
SOCRadar
Sophos
Site Performance Analysis

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 Good 50-89 Needs Work 0-49 Poor

Community intelligence

1 community report

CategoryIMPERSONATION

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

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 14 det. ChainPatrol ChainAbuse 1 report URLQuery Open lookup SSL Labs Stored TLS valid CF Radar Open report OTX 4 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Community Scam Report — ChainAbuse
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.
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks Deep Analysis

Were You Affected by This Site?

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

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Europol
Find the official reporting channel for your EU country
National police directory
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory
Template-based draft • optional AI wording assistance requires separate consent Review and submit it yourself

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

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