Skip to security report
Analytics Dashboard
Domain security report
trezarsuiteapp.wasmer.app favicon

trezarsuiteapp.wasmer.app

“Official Trezor Suite Desktop & Web App for Hardware Wallet”

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: 5/89 Automated brand label: Trezor
Sep 13, 2026 Trezor
API
Registrar
Wasmer
Resolved IP
62.210.172.150
Registered
Oct 16, 2018
2 sources
The capture source is temporarily unavailable.
1 / 2
Source
Primary capture
Collected · UTC
Open capture
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 5. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

VirusTotal
VirusTotal
5 det.
CF Radar
Malicious
URLScan
URLScan
Report ↗
ScamAdviser
Scamadviser
15/100Very Likely Unsafe
TLS Certificate
Within stored validity dates 26d
Let's Encrypt / YE1 · Hostname coverage not recorded
Age
8 yr
Observed status
Content unavailable 410
PhishDestroy
DestroyList
Listed

Source evidence

8 · 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

5 / 89

Report
Interpretation & limits

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

CF Radar

provider verdict: malicious

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 verdict

malicious

Report
Interpretation & limits

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

Scamadviser

15/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.

OTX

no community references

Report
Interpretation & limits

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

URLScan capture

stored report

View stored capture ↗
Observation time not recorded
Report
Interpretation & limits

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

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.

Public blocklists

0 external matches

Details
Interpretation & limits

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

Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing
View full Cloudflare Radar report

Evidence Summary

Critical
VirusTotal
5/89
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

trezarsuiteapp.wasmer.app returned HTTP status 410 in an HTTP check dated 2026-10-01, a recorded response indicating the resource was reported as gone at that time. The same domain appears in the publisher-owned PhishDestroy catalogue, a listing recorded separately from the HTTP check.

Recorded Evidence

The HTTP check on 2026-10-01 recorded status 410 for trezarsuiteapp.wasmer.app. PhishDestroy's internal listing records the domain in its own catalogue. VirusTotal recorded 5 detections across 89 scanners on 2026-09-13. The domain was first observed on 2026-09-13, and a PageSpeed check that same date returned a performance score of 100. An SSL scan on 2026-09-14 recorded the issuer as Let's Encrypt / YE1. The resolved IP address 62.210.172.150 is recorded in France under the organization ONLINE.

Interpretation

These records describe separate observations made by different sources on different dates, and each source measures something distinct. The HTTP status, the PhishDestroy listing, the VirusTotal detection count and the PageSpeed score are not interchangeable and should not be merged into a single conclusion. The chronology shows first observation and PageSpeed on one date, an SSL scan the next day, and the HTTP check roughly two and a half weeks later, so the records are sequential rather than simultaneous.

Recommended Actions

Preserve the PhishDestroy listing, the VirusTotal record and the HTTP check for trezarsuiteapp.wasmer.app as separate source records. Compare the HTTP response and the PhishDestroy listing against future checks of the same domain to see whether the recorded observations change. Retain the PageSpeed and SSL scan records alongside them so any later comparison uses the same set of sources.

Data coverage & collection

22 · datasets with records / 9 · 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
5 / 89 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
0 · external matches
Cloudflare Radar
maliciousCollection time not recorded
Scamadviser
15/100 · provider trust scoreCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
WasmerCollection time not recorded
Network & DNS
62.210.172.150 · 1 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt / YE1
Page captures
2 · retained captures
Page analysis
2 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
100/100 · mobile performance
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
Wayback archive
Archive link retained
Not recorded in this report 9

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

  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • HTML archives
  • Site configuration files
  • Response records
  • Recorded subdomains
  • Community reports
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Public Blocklist Status

Domain, network & archive

Wasmer · 62.210.172.150 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Trezor report ↗
IP Reputation abuse score 0/100 0 reports checked Sep 13, 2026
Registrar (base domain) Wasmer
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for wasmer.app →
Registration (base domain)wasmer.app · Created Oct 16, 2018
HTTP Status410 Gone
Time to First Unavailability 21h
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 13, 2026
DOM Analysisanalyzed Sep 14, 2026score 78/1002 brand signals
Submitted URLhttp://trezarsuiteapp.wasmer.app/
Favicon Hash
ICANN OVERSIGHT Registration: wasmer.app

Accreditation and RAA context
Registrar accreditation and DNS abuse obligations

For the registrable domain wasmer.app behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
62.210.172.150
Network ASN
AS12876
Organization
ONLINE
Observed location
Paris, FR
Nameservers 1
  • beta.ns.wasmernet.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-08-14 13:07:41
Valid until
2026-11-12 13:07:40
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-09-13 22:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprintb22cbf855d708f012eaa0a3c4a93d9a90348d61bd926cf938f38954f00a626e6

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

viewdns.info · 62.210.172.150rapiddns.io

Latest Classified Outcome 2026-10-15 01:13:03 UTC

Primary outcome Unknown reason: Stale Current Evidence 0% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Unknown Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Inactive Http No Content 70% 2026-10-15 01:13:03 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-09-13 22:00:16 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

5 / 89 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
ESET
Fortinet
Kaspersky
PhishFort

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of trezarsuiteapp.wasmer.app · checked Sep 13, 2026

100
Good
Performance
FCP
0.8s
First Contentful Paint
LCP
0.8s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.36s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details1

Availability observations

Last reachable observation

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: dead_http: raw=http_410; http=410; via=https_proxy

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
Cloaked / Filtered

Timeline & response

Collection history, report status and investigation channels

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-14 10:00:20 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  2. Threat First Observed 2026-09-13 12:36:49 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as unknown pointing to IP 62.210.172.150.
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

    inactive→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  3. Availability monitor · Recorded state

    inactive→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  5. Availability monitor · Recorded state

    inactive→Unknown

    probe_inconclusive

Earlier observations 12
  1. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  2. Availability monitor · Recorded state

    inactive→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  4. Availability monitor · Recorded state

    inactive→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  6. Availability monitor · Recorded state

    inactive→Unknown

    probe_inconclusive

  7. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  8. Availability monitor · Recorded state

    inactive→Unknown

    probe_inconclusive

  9. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  10. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  11. Availability monitor · Recorded state

    Reachable→Unavailable

  12. Availability monitor · First collection record

    Unknown

Threat Response Pipeline

Discovery
Analysis
Monitoring

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

Threat Ingested
trezarsuiteapp.wasmer.app detected and queued for full analysis
Sep 13, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
URLScan Verdict
URLScan returned a malicious verdict · score 100
Sep 14, 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.
Web Archive
Preserved in Wayback Machine — historical evidence archived
Sep 24, 2026
VirusTotal
5/89 recorded on VirusTotal
Sep 13, 2026
CF Radar: Malicious
Cloudflare Radar classified this domain as phishing
Brand Impersonation
Impersonation of Trezor
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 410); the cause was not independently established.
Sep 14, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Sep 13, 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 14, 2026
Time to First Unavailability
21 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

Brand abuse: impersonation, fake affiliation, impersonating Trezor

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 5 det. ChainPatrol ChainAbuse 1 report URLQuery Scamadviser 15 trust SSL Labs Hostname coverage not recorded CF Radar Malicious WOT Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Third-Party Detection — ChainAbuse
1 report filed for trezarsuiteapp.wasmer.app · category: Impersonation · source checked
Flagged by automated brand-abuse detection on Sep 13, 2026 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
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 Archived
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?

4 evidence signal groups linked 0 stored notification records Content unavailable

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.

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 trezarsuiteapp.wasmer.app)
  • 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: trezarsuiteapp.wasmer.app

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “Official Trezor Suite Desktop & Web App for Hardware Wallet”. Apparent target: Trezor.

VirusTotal detections for trezarsuiteapp.wasmer.app: 5 (2026-09-13 12:37:04 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/trezarsuiteapp.wasmer.app"
  title="PhishDestroy threat report for trezarsuiteapp.wasmer.app"
  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>