Skip to security report
Analytics Dashboard
Domain security report
trezor-s.io favicon

trezor-s.io

“Security Check”

Threat verdict
CriticalDomain Appeal
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
Risk signals
VirusTotal detections: 7/89 Spamhaus DBL: DBL_SPAM Stored blocklist matches: 2 URLQuery threat systems: 2 alerts Automated brand label: Trezor
OTX: 3 refs Sep 19, 2026 Trezor 1 Report Sent
API
Registrar
Gransy, s.r.o
Resolved IP
45.74.7.27
Registered
Aug 28, 2026
4 sources
The capture source is temporarily unavailable.
1 / 4
Source
Primary capture
Collected · UTC
Open capture
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 7. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

Spamhaus DBL
DBL_SPAM
VirusTotal
VirusTotal
7 det.
URLQuery
URLQuery
2 threat alerts
OTX references
3 community refs
URLScan
URLScan
Report ↗
ScamAdviser
Scamadviser
80/100Likely Safe
TLS Certificate
Within stored validity dates
Let's Encrypt / YR2 · Hostname coverage not recorded
Age
2 mo New
Observed status
Content unavailable
PhishDestroy
DestroyList
Listed
Reports Sent
1

Source evidence

10 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

7 / 89

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLQuery

2 threat-system alerts

Report
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

URLScan verdict

malicious

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Public blocklists

2 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Spamhaus DBL

DBL_SPAM

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

3 community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

Scamadviser

80/100

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Network Security Intelligence
Threat Detection Systems 2 alerts
Detection System Indicator Verdict Alert
DNS4EU trezor-s.io malicious Sinkholed
OpenDNS trezor-s.io phishing Phishing Block
Stored URLQuery scan evidence · Sep 19, 2026 07:32 UTC Open source report

Evidence Summary

Critical
VirusTotal
7/89
OTX
3 community refs
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Assessment

Stored evidence for trezor-s.io: VirusTotal recorded 7 detections among 89 scanners on 2026-09-19. 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 trezor-s.io. Each item in this report remains at the scope supplied by its dated source record.

Detection Evidence

VirusTotal records 7 detections among 89 scanners in the stored snapshot dated 2026-09-19. 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-19 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 trezor-s.io in the snapshot dated 2026-09-19. 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 trezor-s.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 trezor-s.io on 2026-09-19. The MetaMask and SEAL blocklist snapshot is dated 2026-09-19 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-08-28. A URLScan reference was stored on 2026-09-19 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

For trezor-s.io, the registrar field records Gransy, s.r.o.; this is kept as an exact source value. The source stores 45.74.7.27 as the observed address in this record. The registration date for trezor-s.io is recorded as 2026-08-28. 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 trezor-s.io record states that VirusTotal recorded 7 detections among 89 scanners on 2026-09-19. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-19. PhishDestroy remains a separate publisher catalogue entry in the stored record. For trezor-s.io, the registrar field records Gransy, s.r.o.; this remains separate from the other source fields. The observed address field in this record contains 45.74.7.27. The supported conclusion is bounded to the exact stored observations for trezor-s.io. Any statement beyond those source values would require additional dated material.

Recommended Actions

Avoid submitting sensitive information to trezor-s.io during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain trezor-s.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 trezor-s.io. The stored record does not justify extending that rule to 45.74.7.27 or to other infrastructure records.

Data coverage & collection

21 · datasets with records / 10 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
7 / 89 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
2 · recorded detections / alerts
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
3 · community references
External blocklists
2 · external matches
Cloudflare Radar
cleanCollection time not recorded
Scamadviser
80/100 · provider trust scoreCollection time not recorded
Spamhaus DBL
DBL_SPAM
Domain registration
Gransy, s.r.o.Collection time not recorded
Network & DNS
45.74.7.27 · 2 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt / YR2
Page captures
4 · retained captures
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
Response records
1 · outgoing report records
Availability history
15 · stored state changes
Source observation history
2 · stored source events
Lookalike relationships
74 · retained relationshipsCollection time not recorded
Chainabuse records
1 · recorded reports
IP reputation
Network-level observations
Not recorded in this report 10

These checks have no retained result. This does not mean they passed or that a scan is running.

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • HTML archives
  • Page analysis
  • Site configuration files
  • PageSpeed performance
  • Recorded subdomains
  • Community reports
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

2 · external source matches

Public Blocklist Status

Domain, network & archive

Gransy, s.r.o. · 45.74.7.27 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Trezor report ↗
IP Reputation abuse score 14/100 184 reports Phishing checked Sep 19, 2026
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Gransy, s.r.o (Unknown)
Abuse contactabuse@virtualine.org
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for trezor-s.io →
RegistrationCreated Aug 28, 2026 (49d · New) — Expires Aug 28, 2027
Time to First Unavailability 3 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 detailsProvenance & timestamps
First DetectedSep 19, 2026
Submitted URLhttp://trezor-s.io/
Favicon Hash
Case ID

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
45.74.7.27
Network ASN
AS202412
Organization
Virtualine Technologies
Observed location
London, GB
Server header
openresty
Nameservers 2
  • breeze.majahan.com
  • juniper.majahan.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-08-28 15:59:56
Valid until
2026-11-26 15:59:55
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-09-19 10:02:15 UTC
Collection source
PhishDestroy collector
Certificate fingerprint998baf36d2940e8dd4eef8e431896d0fc9cf71b978a3e04d50d7c6b4d7f59574

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

viewdns.info · 45.74.7.27rapiddns.io

Latest Classified Outcome 2026-10-15 20:22:19 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-15 01:16:20 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-09-21 22:48:19 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-09-21 22:48:19 UTC → 2026-09-30 16:14:55 UTC · 209.44h midpoint estimate ≈ 2026-09-26 07:31:37 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.
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

7 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 7 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
Kaspersky
LevelBlue
PhishFort
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
209.44
Estimate basis
Bounded by observations
Estimate precision
Low

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

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

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: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='trezor-s.io', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO

Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
Saved result
Keitaro TDS

Timeline & response

1 · outbound report records

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. Domain Status Transition 2026-09-22 10:48:51 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  2. Threat First Observed 2026-09-19 07:11:48 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 45.74.7.27.
Stored observation history17

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

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

Earlier observations 12
  1. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  6. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  8. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  9. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  10. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  11. Availability monitor · Recorded state

    Reachable→Unavailable

  12. Availability monitor · First collection record

    Reachable

Threat Response Pipeline

Discovery
Analysis
Notifications
Monitoring

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

Threat Ingested
trezor-s.io detected and queued for full analysis
Sep 19, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_SPAM
Sep 19, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Sep 19, 2026
URLScan Verdict
URLScan returned a malicious verdict · score 100
Sep 22, 2026
Cloudflare Radar Report
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.
VirusTotal
7/89 recorded on VirusTotal
Sep 19, 2026
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 16, 2026
OTX Community References
3 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Sep 19, 2026
Brand Impersonation
Impersonation of Trezor
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Sep 19, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 16, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 404); the cause was not independently established.
Sep 22, 2026
Sent Report Recorded
Stored outgoing record associated with registrar Gransy, s.r.o., 1 abuse contact
abuse@virtualine.org
Sep 19, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Sep 19, 2026
Content Observed Unavailable
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 22, 2026
Time to First Unavailability
75 hours elapsed from detection to the first unavailable observation.
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.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

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 SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP 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

Related infrastructure

Shared hosting, registrar records and related domains

Lookalike domains

74 stored lookalike domains

treaor.io replacement Internal report treozr.io transposition Internal report trzezor.io insertion Internal report trzor.io omission Internal report rtrezor.io insertion Internal report terezor.io insertion Internal report trazor.io bitsquatting Internal report trexzor.io insertion Internal report trezort.io addition Internal report 5rezor.io replacement 6rezor.io replacement frezor.io replacement
Show all (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

Community records

Retained community reports and observations

Community intelligence

1 community report

CategoryIMPERSONATION

Phishing: impersonation, fake affiliation, cloaking, seo poisoning, impersonating Trezor

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 7 det. ChainPatrol ChainAbuse 1 report URLQuery 2 threat alerts Scamadviser 80 trust SSL Labs Hostname coverage not recorded CF Radar Open report OTX 3 refs WOT Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Community Scam Report — ChainAbuse
1 report filed for trezor-s.io (1 written by a person) · category: Impersonation · source checked
“Phishing: impersonation, fake affiliation, cloaking, seo poisoning, impersonating Trezor”
— reported by Anonymous Trusted reporter on Sep 18, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260919-13E2A8 Recipient: abuse@virtualine.org
Page title stored with report: Security Check
Blocklist hits included with submission: MetaMask, SEAL
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider 
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
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
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

7 evidence signal groups linked 1 stored notification records Content unavailable
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.

Immediate steps Find reporting contacts
Official reporting routes
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

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

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.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including trezor-s.io)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

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?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

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

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
Read the evidence in context

About This Report: trezor-s.io

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “Security Check”. Apparent target: Trezor.

VirusTotal detections for trezor-s.io: 7 (2026-09-19 07:44:34 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

submit an appeal or review the FAQ page.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

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