Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 3/92 engines flagged. malicious: 3. suspicious: 0. Analysis time (as stored): 2026-11-05T18:07:45Z. Retrieved (as stored): 2026-11-06T23:37:13Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
trezor.io-start.app favicon

trezor.io-start.app

In short

On 2026-11-06, trezor.io-start.app displayed a dashboard page branded with the Trezor name and logo. The main panel shows an illustration of a laptop connected to a hardware wallet, with the heading "Connect your Trezor" and the text "Connect your Trezor to manage your crypto assets securely." A green Connect button sits below this prompt. A left sidebar lists Dashboard, Swap, Earn, Notifications, and Settings, with Dashboard highlighted as the active view.

“Trezor Suite App (Official) | Manage Your Trezor Wallet”

Review the evidence
Registrar
SwedenName.com
Resolved IP
Russia201.24.113.193JSC "TIMEWEB"
Registered
Nov 13, 2025
First observed
Nov 7, 2026
PhishDestroy assessment High
69/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 3/92 Spamhaus DBL: DBL_ABUSED_PHISH
VirusTotal
3 / 92
engine detections ·
Cloudflare Radar
Phishing
Page captures
6
open gallery
Domain age
360 days
registered 2025-11-13 according to WHOIS · source data differ
Nov 7, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded trezor.io-start.app on 2026-11-06. Stored VirusTotal result: 3/92 engines flagged. malicious: 3. suspicious: 0. Analysis time (as stored): 2026-11-05T18:07:45Z. Retrieved (as stored): 2026-11-06T23:37:13Z. Risk: high (69/100). Registrar: Name.com. Status: Last known active. Hosting: JSC "TIMEWEB". Do not enter credentials or connect a wallet.

High
Status
Last known active
VirusTotal
3 / 92
Hosting
Russia201.24.113.193JSC "TIMEWEB"
Registrar
SwedenName.com
Registered
Nov 13, 2025
Page captures
6
Page captures Source results Registration record

Capture recorded with this analysis · Cloudflare Radar · 2026-11-06T23:38:13Z
SHA-256: 2a9863bb630c9ca2f7e20de65c2156e27f213bb81eb3bf765d41bfcff4cf8745

PhishDestroy analysis, reviewed version

On 2026-11-06, trezor.io-start.app displayed a dashboard page branded with the Trezor name and logo. The main panel shows an illustration of a laptop connected to a hardware wallet, with the heading "Connect your Trezor" and the text "Connect your Trezor to manage your crypto assets securely." A green Connect button sits below this prompt. A left sidebar lists Dashboard, Swap, Earn, Notifications, and Settings, with Dashboard highlighted as the active view.

The stored VirusTotal domain result reports 3 detections out of 92 engines. VIPRE reported "phishing"; SOCRadar reported "phishing".

Source evidenceVirusTotal 3 / 92 8 sources

VirusTotal

3 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
58
Malicious
3
Suspicious
0
Undetected
31

Vendor labels

VIPRE
phishing
SOCRadar
phishing
Gridinsoft
phishing

Reputation score

0

Created

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    201.24.113.193

DNS records observed

JARM fingerprint

1dd40d40d00040d00042d43d000000831b6af40378e2dd35eeac4e9311926e

Certificate

Subject alternative names
  • trezor.io-start.app
Issuer
Let's Encrypt / YE1
Serial
667b58a48a1436f497b5cdd9e7acd1437b8
SHA-256
8a2c7f4bdc0583789478ce3f60fce264ccda6cd70b224fccca79cbd8261a2567
Subject
trezor.io-start.app
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 58,
    "malicious": 3,
    "suspicious": 0,
    "undetected": 31
}
Vendor labels
{
    "VIPRE": "phishing",
    "SOCRadar": "phishing",
    "Gridinsoft": "phishing"
}
Reputation
0
Created
2025-11-13T00:00:00Z
Updated
2025-11-13T00:00:00Z
First seen
2026-01-14T01:00:09Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "201.24.113.193"
    }
]
Dns at
2026-11-05T18:19:42Z
Jarm
1dd40d40d00040d00042d43d000000831b6af40378e2dd35eeac4e9311926e
Certificate
{
    "san": [
        "trezor.io-start.app"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "667b58a48a1436f497b5cdd9e7acd1437b8",
    "sha256": "8a2c7f4bdc0583789478ce3f60fce264ccda6cd70b224fccca79cbd8261a2567",
    "subject": "trezor.io-start.app",
    "valid_to": "2027-02-03T16:59:03Z",
    "valid_from": "2026-11-05T16:59:04Z"
}
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

source
VirusTotal
scope
unknown
result_state
observed
numerator
3
denominator
92
malicious
null
suspicious
null
vendors
["Gridinsoft","SOCRadar","VIPRE"]
observed_at
2026-11-05 18:07:45
checked_at
2026-11-07 00:37:14
fetched_at
2026-11-06 23:37:14
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

e443ac36-e1dd-43bc-b859-939dec82191a

Final URL

https://trezor.io-start.app/

HTTP response

200

Navigation history

  • URL
    https://trezor.io-start.app/
    Status
    200

DOM structure hash

bf91af3af4c8b18124319d5b77e73a6e44372d479b503c99c8ea71fa8eee8200

Document hash

f6ae75f39c578479b428a2465e71a854d6866c663f9e3d3663ae48d94ddaf925

Phishing classifier result

  • phishing

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    trezor.io-start.app
    Type
    A
    Value
    201.24.113.193

DNSSEC valid

No

IP address

127.0.1.1

127.0.1.1 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Original source fields · JSON
Uuid
e443ac36-e1dd-43bc-b859-939dec82191a
Final url
https://trezor.io-start.app/
Status
200
History
[
    {
        "url": "https://trezor.io-start.app/",
        "status": 200
    }
]
DOM structure hash
bf91af3af4c8b18124319d5b77e73a6e44372d479b503c99c8ea71fa8eee8200
Document hash
f6ae75f39c578479b428a2465e71a854d6866c663f9e3d3663ae48d94ddaf925
Phishing v2
[
    "phishing"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "trezor.io-start.app",
        "type": "A",
        "value": "201.24.113.193"
    }
]
Dnssec valid
false
Ip
127.0.1.1

127.0.1.1 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Separate stored summary: clean · observation date not recorded

This summary differs from the dated scan above. It is retained for provenance and does not override the selected source observation.

verdict
clean
categories
[]
observed_at
null
source_path
phishdestroy.technologies.cf_radar
scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

Spamhaus DBL

DBL_ABUSED_PHISH

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

SHA-256 6f1891b9047a8d85a12800174051f70e569a9ce831c5acc4e9cc93be88bfa9ec

Open report
URLScanOriginal source recordObserved: 8 fields

Observed: · Retrieved:

Report ID

01a198ea-7632-7642-98e3-09f308a90a67

Final URL

http://trezor.io-start.app/

Redirects

  • To
    https://trezor.io-start.app/
    From
    http://trezor.io-start.app/
    Status
    307

JavaScript globals

  • assert
  • getRequiredElement
  • P
  • S
  • getRandomNum
  • getTimeStamp
  • Dimensions
  • Config$2
  • getGlobalConfig
  • setGlobalConfig
  • Config$1
  • Config
  • setMaxGapCoefficient
  • setMaxObstacleLength
  • Status
  • A11yStrings
  • RunnerClasses
  • RunnerSounds
  • RunnerEvents
  • updateCanvasScaling
  • getA11yString
  • vibrate
  • createCanvas
  • decodeBase64ToArrayBuffer
  • createAdjustedCollisionBox
  • drawCollisionBoxes
  • boxCompare
  • toggleHelpBox
  • diagnoseErrors
  • portalSignin
  • updateForDnsProbe
  • getMainFrameErrorCssClass
  • getMainFrameErrorIconCssClass
  • getSubFrameErrorIconCssClass
  • shouldShowSuggestionsSummaryList
  • getSuggestionsSummaryItemCssClass
  • reloadButtonClick
  • downloadButtonClick
  • detailsButtonClick
  • setAutoFetchState

Domain age, days

2025

Differs from the registration date in WHOIS (2025-11-13), which gives 353 days on the scan date 2026-11-01. The two sources disagree; both values are kept as recorded.

Registered domain age, days

2025

Differs from the registration date in WHOIS (2025-11-13), which gives 353 days on the scan date 2026-11-01. The two sources disagree; both values are kept as recorded.

Page requests

5

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
-61
Malicious
No
Overall verdict
Score
0
Malicious
No
Original source fields · JSON
Uuid
01a198ea-7632-7642-98e3-09f308a90a67
Final url
http://trezor.io-start.app/
Redirects
[
    {
        "to": "https://trezor.io-start.app/",
        "from": "http://trezor.io-start.app/",
        "status": 307
    }
]
Globals
[
    "assert",
    "getRequiredElement",
    "P",
    "S",
    "getRandomNum",
    "getTimeStamp",
    "Dimensions",
    "Config$2",
    "getGlobalConfig",
    "setGlobalConfig",
    "Config$1",
    "Config",
    "setMaxGapCoefficient",
    "setMaxObstacleLength",
    "Status",
    "A11yStrings",
    "RunnerClasses",
    "RunnerSounds",
    "RunnerEvents",
    "updateCanvasScaling",
    "getA11yString",
    "vibrate",
    "createCanvas",
    "decodeBase64ToArrayBuffer",
    "createAdjustedCollisionBox",
    "drawCollisionBoxes",
    "boxCompare",
    "toggleHelpBox",
    "diagnoseErrors",
    "portalSignin",
    "updateForDnsProbe",
    "getMainFrameErrorCssClass",
    "getMainFrameErrorIconCssClass",
    "getSubFrameErrorIconCssClass",
    "shouldShowSuggestionsSummaryList",
    "getSuggestionsSummaryItemCssClass",
    "reloadButtonClick",
    "downloadButtonClick",
    "detailsButtonClick",
    "setAutoFetchState"
]
Domain age days
2025

Differs from the registration date in WHOIS (2025-11-13), which gives 353 days on the scan date 2026-11-01. The two sources disagree; both values are kept as recorded.

Apex age days
2025

Differs from the registration date in WHOIS (2025-11-13), which gives 353 days on the scan date 2026-11-01. The two sources disagree; both values are kept as recorded.

Requests
5
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": -61,
        "malicious": false
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
Separate monitor record · 2026-11-07 04:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a198ea-7632-7642-98e3-09f308a90a67
score
0
malicious
false
result_at
2026-11-07T04:30:10Z
enriched_at
2026-11-07T09:11:49Z
source_timestamps
{"urlscan_result_at":"2026-11-07 05:30:10","urlscan_enriched_at":"2026-11-07 10:11:49"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy DOM

10 / 100 · heuristic score · 1 brand reference · 0 classifications

Open report
Separate monitor score · 10 / 100 · 2026-11-06T23:52:01Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
10
analyzed_at
2026-11-06T23:52:01Z
source_timestamp
2026-11-07 00:52:01
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
trezor.io-start.app: Recorded Trezor Wallet Dashboard Connection Page
ai_description
PhishDestroy records trezor.io-start.app showing a Trezor-branded dashboard page that prompts visitors to connect a Trezor device to manage crypto assets.
ai_summary
On 2026-11-06, trezor.io-start.app displayed a dashboard page branded with the Trezor name and logo. The main panel shows an illustration of a laptop connected to a hardware wallet, with the heading "Connect your Trezor" and the text "Connect your Trezor to manage your crypto assets securely." A green Connect button sits below this prompt. A left sidebar lists Dashboard, Swap, Earn, Notifications, and Settings, with Dashboard highlighted as the active view. The stored VirusTotal domain result reports 3 detections out of 92 engines. VIPRE reported "phishing"; SOCRadar reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-07 00:40:16
revision
d91d6a906dfba22a455ca4433d4aecdb723feba1c1c32d9d9f6a9a5c1feeb6da
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 25 fields

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
49366

Crawler rules

User agents
  • *
  • Yandex
  • bingbot
  • msnbot
Present
Yes
Sitemap URLs
  • https://trezor.io-start.app/sitemap.xml

Sitemap

Present
Yes
URL count
1

Page title and metadata

Open Graph URL
https://trezor.io-start.app/
Page title
Trezor Suite App (Official) | Manage Your Trezor Wallet
Open Graph type
website
Indexing directives
index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1
Open Graph image
https://trezor.io-start.app/og-image.jpg
Open Graph title
Trezor Suite App (Official) | Manage Your Trezor Wallet
Keywords
trezor suite, trezor wallet, trezor suite app, trezor suite download, trezor io start, trezor safe 5, hardware wallet, crypto wallet, bitcoin wallet trezor, ethereum trezor
Open Graph site name
Trezor Suite
Description
Trezor Suite is the official app for Trezor hardware wallets. Manage Bitcoin, Ethereum and 5000+ coins. Secure crypto management at trezor.io/start.
Twitter card
summary_large_image
Canonical URL
https://trezor.io-start.app/
Open Graph description
Trezor Suite is the official app for Trezor hardware wallets. Manage Bitcoin, Ethereum and 5000+ coins. Secure crypto management at trezor.io/start.

Trackers

Requests
6
Observed services
  • Name
    Yandex
    Company
    Yandex
    Country
    RU
    Category
    Advertising
    Requests
    1
  • Name
    Yandex Metrika
    Company
    Yandex
    Country
    RU
    Category
    Site Analytics
    Requests
    1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
129
TLS
104
Waiting
95
Connection
47
Download
142
Response time, ms
517

TLS connection

ALPN
http/1.1
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 22
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
130909
CO₂, grams
0.0048
Cleaner than, %
16

DNS servers

Nameservers
  • IP address
    108.162.192.240
    Host
    wanda.ns.cloudflare.com
  • IP address
    108.162.195.50
    Host
    damian.ns.cloudflare.com
DNS zone
io-start.app

Cookies

Cookies
  • Name
    bh
    Secure
    Yes
    SameSite
    None

Location

IP address
201.24.113.193
ASN
9123
Organization
JSC "TIMEWEB"
City
Moscow
Country
RU

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
trezor.io-start.app

DNS records

A
  • 201.24.113.193

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
SAMEORIGIN
Referrer-Policy
strict-origin-when-cross-origin
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
201.24.113.193
IP version
4

Redirects

Redirect chain
  • https://trezor.io-start.app

Subdomains

Count
1
Subdomains
  • trezor.io-start.app

Technology stack

Technologies
  • Ubuntu
  • Nginx
  • Yandex.Metrika
  • Open Graph

Page links

External link addresses
  • https://trezor.io/
External links
1
Internal links
6

HTTP headers

Response headers
Server
nginx/1.28.3 (Ubuntu)
Content-type
text/html; charset=utf-8
X-frame-options
SAMEORIGIN
X-content-type-options
nosniff
Referrer-policy
strict-origin-when-cross-origin
Content-language
en
X-cache
HIT
Original source fields · JSON
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-11-06T23:37:22Z",
    "first": "2026-11-06T23:37:22Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 49366
}
Crawler rules
{
    "agents": [
        "*",
        "Yandex",
        "bingbot",
        "msnbot"
    ],
    "present": true,
    "sitemaps": [
        "https://trezor.io-start.app/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 1
}
Page title and metadata
{
    "ogUrl": "https://trezor.io-start.app/",
    "title": "Trezor Suite App (Official) | Manage Your Trezor Wallet",
    "ogType": "website",
    "robots": "index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1",
    "ogImage": "https://trezor.io-start.app/og-image.jpg",
    "ogTitle": "Trezor Suite App (Official) | Manage Your Trezor Wallet",
    "keywords": "trezor suite, trezor wallet, trezor suite app, trezor suite download, trezor io start, trezor safe 5, hardware wallet, crypto wallet, bitcoin wallet trezor, ethereum trezor",
    "ogSiteName": "Trezor Suite",
    "description": "Trezor Suite is the official app for Trezor hardware wallets. Manage Bitcoin, Ethereum and 5000+ coins. Secure crypto management at trezor.io/start.",
    "twitterCard": "summary_large_image",
    "canonicalUrl": "https://trezor.io-start.app/",
    "ogDescription": "Trezor Suite is the official app for Trezor hardware wallets. Manage Bitcoin, Ethereum and 5000+ coins. Secure crypto management at trezor.io/start."
}
Trackers
{
    "requests": 6,
    "trackers": [
        {
            "name": "Yandex",
            "company": "Yandex",
            "country": "RU",
            "category": "Advertising",
            "requests": 1
        },
        {
            "name": "Yandex Metrika",
            "company": "Yandex",
            "country": "RU",
            "category": "Site Analytics",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 129,
        "tls": 104,
        "wait": 95,
        "connect": 47,
        "download": 142
    },
    "response_ms": 517
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 130909,
    "co2_grams": 0.0048,
    "cleaner_than": 16
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.192.240",
            "host": "wanda.ns.cloudflare.com"
        },
        {
            "ip": "108.162.195.50",
            "host": "damian.ns.cloudflare.com"
        }
    ],
    "zone": "io-start.app"
}
Cookies
{
    "cookies": [
        {
            "name": "bh",
            "secure": true,
            "same_site": "None"
        }
    ]
}
Location
{
    "ip": "201.24.113.193",
    "asn": "9123",
    "org": "JSC \"TIMEWEB\"",
    "city": "Moscow",
    "country": "RU"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "trezor.io-start.app"
}
DNS records
{
    "A": [
        "201.24.113.193"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": "SAMEORIGIN",
    "referrerPolicy": "strict-origin-when-cross-origin",
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "201.24.113.193",
    "family": 4
}
Redirects
{
    "chain": [
        "https://trezor.io-start.app"
    ]
}
Subdomains
{
    "count": 1,
    "subdomains": [
        "trezor.io-start.app"
    ]
}
Tech stack
{
    "technologies": [
        "Ubuntu",
        "Nginx",
        "Yandex.Metrika",
        "Open Graph"
    ]
}
Page links
{
    "external": [
        "https://trezor.io/"
    ],
    "external_count": 1,
    "internal_count": 6
}
HTTP headers
{
    "headers": {
        "server": "nginx/1.28.3 (Ubuntu)",
        "content-type": "text/html; charset=utf-8",
        "x-frame-options": "SAMEORIGIN",
        "x-content-type-options": "nosniff",
        "referrer-policy": "strict-origin-when-cross-origin",
        "content-language": "en",
        "x-cache": "HIT"
    }
}

Questions about trezor.io-start.app

Is trezor.io-start.app legit?

PhishDestroy rates trezor.io-start.app as high risk (69/100) from the recorded evidence; it was first recorded on 2026-11-06. Stored VirusTotal result: 3/92 engines flagged. malicious: 3. suspicious: 0. Analysis time (as stored): 2026-11-05T18:07:45Z. Retrieved (as stored): 2026-11-06T23:37:13Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is trezor.io-start.app safe to connect a wallet?

This report does not record which wallet requests trezor.io-start.app makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used trezor.io-start.app?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 6 captures

Cloudflare Radar 1 / 6 Used in the analysis Source file SHA-256: 2a9863bb630c9ca2f7e20de65c2156e27f213bb81eb3bf765d41bfcff4cf8745 SHA-256 of the prepared copy given to the model: 1a5b0e30219e0cd400034b6ddb4fe3dc64d91de7534c90373f001505ee2da2b8
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://trezor.io-start.app/
Position1 / 6
Open capture Source Report Wayback Download
All capture links and hashes (6)
Observed page title
Trezor Suite App (Official) | Manage Your Trezor Wallet
Automated brand references
Trezor
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 87 days

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation Russia201.24.113.193 abuse score 0/100 0 reports checked Nov 7, 2026
Registrar (base domain) Name.com SE(SE)
Abuse contact["abuse@name.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for io-start.app →
Registration (base domain)io-start.app · Created Nov 13, 2025 (360d) — Expires Nov 13, 2026
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 7, 2026
DOM Analysisanalyzed Nov 7, 2026score 10/1001 brand signal
Submitted URLhttps://trezor.io-start.app/
Favicon Hash
ICANN OVERSIGHT Registration: io-start.app

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain io-start.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
Russia201.24.113.193
Network ASN
AS9123
Organization
JSC "TIMEWEB"
Observed location
RussiaMoscow, RU

Nameservers 2

  • wanda.ns.cloudflare.com
  • damian.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-11-05 16:59:04
Valid until
2027-02-03 16:59:03
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint8a2c7f4bdc0583789478ce3f60fce264ccda6cd70b224fccca79cbd8261a2567
Certificate names · 1 SAN
  • trezor.io-start.app

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

viewdns.info · 201.24.113.193rapiddns.io

Latest Classified Outcome 2026-11-07 23:47:08 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content 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 Live content Ordinary HTTP content served 90% 2026-11-07 23:47:08 UTC
RDAP registration
Observed timeline last reachable: 2026-11-07 11:44:48 UTC last content: 2026-11-07 11:44:48 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.
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

3 / 92 security vendors flagged this domain
View on VT
Last analyzed
VIPRE
SOCRadar
Gridinsoft

Archived Evidence

Wayback Machine Snapshot
View Archive
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Captured network requests

Network requests: 5 SHA-256 hashes: 3 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-06 23:36 UTC.

Open this scan on URLScan 01a198ea-7632-7642-98e3-09f308a90a67 ↗

Stored observation history3

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

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Domain monitor · First collection record

    Reachable

All retained availability observations9

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-08 00:47:08.000000
    Evidence SHA-256
    c34ca3d5896f068ab6a7fa6fbc333f5eb27e2968744ad80f99110d2edab70068
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-08 00:47:08
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-08 00:47:08.000000
    Evidence SHA-256
    c34ca3d5896f068ab6a7fa6fbc333f5eb27e2968744ad80f99110d2edab70068
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-08 00:47:08
    Evidence reason
    alive_content
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 12:44:48.000000
    Evidence SHA-256
    70c3db1df4ffa36aa7d04a7ef20aedde3de6bbf550a3b8fb077634075096dfac
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 12:44:48
    Evidence reason
    alive_content
  4. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 12:44:48.000000
    Evidence SHA-256
    70c3db1df4ffa36aa7d04a7ef20aedde3de6bbf550a3b8fb077634075096dfac
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 12:44:48
    Evidence reason
    alive_content
  5. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 11:22:04.554093
    Evidence SHA-256
    d0d729b70687a3b7d23361551b91f9c7b204c4eac655fb0a10da8512b094b9d2
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 11:22:04.554093
    Evidence reason
  6. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 04:32:14.000000
    Evidence SHA-256
    3814c87de9580e4cbf3384a4827984fea0efccf48ce7cabe0dfdf5065bc74eb5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 04:32:14
    Evidence reason
    alive_content
  7. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 04:32:14.000000
    Evidence SHA-256
    3814c87de9580e4cbf3384a4827984fea0efccf48ce7cabe0dfdf5065bc74eb5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 04:32:14
    Evidence reason
    alive_content
  8. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 00:36:36.000000
    Evidence SHA-256
    48b41b388a00785a0a41b2b37cdce394afde225254bef25fc400b8468684f928
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 00:36:36
    Evidence reason
  9. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 00:36:36.000000
    Evidence SHA-256
    48b41b388a00785a0a41b2b37cdce394afde225254bef25fc400b8468684f928
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 00:36:36
    Evidence reason

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

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

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    trezor.io-start.app detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · Cloudflare Radar Report · Web Archive · VirusTotal · Automated brand label: Trezor · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • Spamhaus DBL
    Spamhaus DBL recorded: DBL_ABUSED_PHISH
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 3/92
  • Automated brand label: Trezor
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

4 entries
  1. Cloudflare Radar

    Phishing

    View source
  2. Wayback Machine

    Page archived

    View source
  3. Added to PhishDestroy

    trezor.io-start.app

    View source
  4. VirusTotal

    3/92 engine detections

    View source
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
All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Lookalike domains

74 stored lookalike domains

Source: dnstwist_results. These are saved variants of target domains. Selection may use older collector labels whose own observation date was not retained. It does not establish impersonation, common ownership or current availability. Dates belong to dnstwist observations; the legacy timezone is not established.

dnstwist_results #480 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 treaor.io replacement Internal report A 185.66.141.35MX treaor.ioNS ns15.knownsrv.com dnstwist_results #502 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 treozr.io transposition Internal report A 185.66.141.35MX treozr.ioNS ns15.knownsrv.com dnstwist_results #464 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trzezor.io insertion Internal report A 185.66.141.35MX trzezor.ioNS ns15.knownsrv.com dnstwist_results #476 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trzor.io omission Internal report A 185.66.141.35MX trzor.ioNS ns15.knownsrv.com dnstwist_results #448 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:13 · Last: 2026-03-17 13:39:13 rtrezor.io insertion Internal report A 185.66.141.35MX rtrezor.ioNS ns15.knownsrv.com dnstwist_results #449 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:13 · Last: 2026-03-17 13:39:13 terezor.io insertion Internal report A 185.66.141.35MX terezor.ioNS ns15.knownsrv.com dnstwist_results #443 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:13 · Last: 2026-03-17 13:39:13 trazor.io bitsquatting Internal report A 77.247.179.89NS ns1.badgerdns.com dnstwist_results #453 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:13 · Last: 2026-03-17 13:39:13 trexzor.io insertion Internal report A 185.66.141.35MX trexzor.ioNS ns15.knownsrv.com dnstwist_results #439 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:13 · Last: 2026-03-17 13:39:13 trezort.io addition Internal report A 185.66.141.35MX trezort.ioNS ns15.knownsrv.com dnstwist_results #491 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 5rezor.io replacement A 91.223.82.8MX 5rezor.ioNS dns3.hostplay.com dnstwist_results #492 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 6rezor.io replacement A 91.223.82.8MX 6rezor.ioNS dns3.hostplay.com dnstwist_results #493 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 frezor.io replacement A 91.223.82.8MX frezor.ioNS dns3.hostplay.com
Show all (62)
dnstwist_results #494 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 grezor.io replacement A 91.223.82.8MX grezor.ioNS dns3.hostplay.com dnstwist_results #471 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 rezor.io omission A 185.66.141.35MX rezor.ioNS ns15.knownsrv.com dnstwist_results #478 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 rrezor.io replacement A 185.66.141.35MX rrezor.ioNS ns15.knownsrv.com dnstwist_results #500 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 rtezor.io transposition A 185.66.141.35MX rtezor.ioNS ns15.knownsrv.com dnstwist_results #495 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 tdezor.io replacement A 91.223.82.8MX tdezor.ioNS dns3.hostplay.com dnstwist_results #479 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 teezor.io replacement A 185.66.141.35MX teezor.ioNS ns15.knownsrv.com dnstwist_results #501 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 terzor.io transposition A 185.66.141.35MX terzor.ioNS ns15.knownsrv.com dnstwist_results #472 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 tezor.io omission A 185.66.141.35MX tezor.ioNS ns15.knownsrv.com dnstwist_results #496 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 tfezor.io replacement A 91.223.82.8MX tfezor.ioNS dns3.hostplay.com dnstwist_results #499 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 tr.ezor.io subdomain A 172.234.24.211MX mx.plingest.comNS dns101.registrar-servers.com dnstwist_results #477 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 tr3zor.io replacement A 104.21.56.17MX dedi4020.your-server.deNS ns1.dns-parking.com dnstwist_results #481 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 treeor.io replacement A 185.66.141.35MX treeor.ioNS ns15.knownsrv.com dnstwist_results #467 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 treezor.io insertion A 213.186.33.5MX mx3.mail.ovh.netNS dns112.ovh.net dnstwist_results #473 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 treor.io omission A 185.66.141.35MX treor.ioNS ns15.knownsrv.com dnstwist_results #497 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 treqor.io replacement A 91.223.82.8MX treqor.ioNS dns3.hostplay.com dnstwist_results #498 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 tresor.io replacement A 91.98.72.43NS ns43.domaincontrol.com dnstwist_results #455 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trezeor.io insertion A 185.66.141.35MX trezeor.ioNS ns15.knownsrv.com dnstwist_results #507 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trezer.io vowel-swap A 104.247.81.99NS ns1.parkingcrew.net dnstwist_results #456 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trezior.io insertion A 185.66.141.35MX trezior.ioNS ns15.knownsrv.com dnstwist_results #482 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trezir.io replacement A 185.66.141.35MX trezir.ioNS ns15.knownsrv.com dnstwist_results #469 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trezkor.io insertion A 91.223.82.8MX trezkor.ioNS dns3.hostplay.com dnstwist_results #470 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trezlor.io insertion A 91.223.82.8MX trezlor.ioNS dns3.hostplay.com dnstwist_results #474 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trezo.io omission A 185.66.141.35MX trezo.ioNS ns15.knownsrv.com dnstwist_results #483 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trezoe.io replacement A 185.66.141.35MX trezoe.ioNS ns15.knownsrv.com dnstwist_results #457 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trezoir.io insertion A 185.66.141.35MX trezoir.ioNS ns15.knownsrv.com dnstwist_results #458 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trezopr.io insertion A 185.66.141.35MX trezopr.ioNS ns15.knownsrv.com dnstwist_results #505 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trezor-io.com various A !ServFailNS !ServFail dnstwist_results #506 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trezorio.com various A 162.255.119.94MX eforward1.registrar-servers.comNS dns1.registrar-servers.com dnstwist_results #484 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trezot.io replacement A 185.66.141.35MX trezot.ioNS ns15.knownsrv.com dnstwist_results #459 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trezpor.io insertion A 185.66.141.35MX trezpor.ioNS ns15.knownsrv.com dnstwist_results #485 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trezpr.io replacement A 185.66.141.35MX trezpr.ioNS ns15.knownsrv.com dnstwist_results #475 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trezr.io omission A 185.66.141.35MX trezr.ioNS ns15.knownsrv.com dnstwist_results #503 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trezro.io transposition A 185.66.141.35MX trezro.ioNS ns15.knownsrv.com dnstwist_results #460 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trezxor.io insertion A 185.66.141.35MX trezxor.ioNS ns15.knownsrv.com dnstwist_results #461 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trezzor.io insertion A 185.66.141.35MX trezzor.ioNS ns15.knownsrv.com dnstwist_results #508 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trizor.io vowel-swap A 172.233.219.123MX mx156.hostedmxserver.comNS ns1.parklogic.com dnstwist_results #509 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trozor.io vowel-swap A 77.247.179.84NS ns1.badgerdns.com dnstwist_results #486 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trrzor.io replacement A 185.66.141.35MX trrzor.ioNS ns15.knownsrv.com dnstwist_results #462 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trtezor.io insertion A 185.66.141.35MX trtezor.ioNS ns15.knownsrv.com dnstwist_results #463 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trwezor.io insertion A 185.66.141.35MX trwezor.ioNS ns15.knownsrv.com dnstwist_results #487 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trwzor.io replacement A 185.66.141.35MX trwzor.ioNS ns15.knownsrv.com dnstwist_results #504 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trzeor.io transposition A 185.66.141.35MX trzeor.ioNS ns15.knownsrv.com dnstwist_results #488 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 trzzor.io replacement A 185.66.141.35MX trzzor.ioNS ns15.knownsrv.com dnstwist_results #489 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 ttezor.io replacement A 185.66.141.35MX ttezor.ioNS ns15.knownsrv.com dnstwist_results #468 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 ttrezor.io insertion A 64.190.63.222MX localhostNS ns1.sedoparking.com dnstwist_results #465 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 tyrezor.io insertion A 185.66.141.35MX tyrezor.ioNS ns15.knownsrv.com dnstwist_results #490 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 yrezor.io replacement A 185.66.141.35MX yrezor.ioNS ns15.knownsrv.com dnstwist_results #466 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:14 · Last: 2026-03-17 13:39:14 ytrezor.io insertion A 185.66.141.35MX ytrezor.ioNS ns15.knownsrv.com dnstwist_results #444 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:13 · Last: 2026-03-17 13:39:13 prezor.io bitsquatting A 81.169.145.163MX smtpin.rzone.deNS docks19.rzone.de dnstwist_results #450 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:13 · Last: 2026-03-17 13:39:13 treazor.io insertion A 185.66.141.35MX treazor.ioNS ns15.knownsrv.com dnstwist_results #451 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:13 · Last: 2026-03-17 13:39:13 trerzor.io insertion A 185.66.141.35MX trerzor.ioNS ns15.knownsrv.com dnstwist_results #452 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:13 · Last: 2026-03-17 13:39:13 trewzor.io insertion A 185.66.141.35MX trewzor.ioNS ns15.knownsrv.com dnstwist_results #442 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:13 · Last: 2026-03-17 13:39:13 trexor.io bitsquatting A 185.66.141.35MX trexor.ioNS ns15.knownsrv.com dnstwist_results #447 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:13 · Last: 2026-03-17 13:39:13 trez0r.io homoglyph NS ridge.ns.cloudflare.com dnstwist_results #454 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:13 · Last: 2026-03-17 13:39:13 trezaor.io insertion A 185.66.141.35MX trezaor.ioNS ns15.knownsrv.com dnstwist_results #441 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:13 · Last: 2026-03-17 13:39:13 trezora.io addition A 44.227.65.245MX mx1.hostinger.comNS curitiba.ns.porkbun.com dnstwist_results #437 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:13 · Last: 2026-03-17 13:39:13 trezore.io addition A 185.66.141.35MX trezore.ioNS ns15.knownsrv.com dnstwist_results #436 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:13 · Last: 2026-03-17 13:39:13 trezoro.io addition A 100.50.228.214MX alt1.aspmx.l.google.comNS ns-1000.awsdns-61.net dnstwist_results #438 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:13 · Last: 2026-03-17 13:39:13 trezorr.io addition A 185.66.141.35MX trezorr.ioNS ns15.knownsrv.com dnstwist_results #440 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:13 · Last: 2026-03-17 13:39:13 trezors.io addition A 208.98.35.100MX igw08.site4now.netNS ns1.site4now.net dnstwist_results #446 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:13 · Last: 2026-03-17 13:39:13 xn--tezor-5bb.io homoglyph A 91.215.85.162NS ns3.my-ndns.com dnstwist_results #445 · Target: trezor.io · target_brand label · First: 2026-03-17 13:39:13 · Last: 2026-03-17 13:39:13 xn--trezo-9bb.io homoglyph A 145.249.115.168NS ns3.my-ndns.com

Community intelligence

3 community reports

CategoryImpersonation

Brand abuse: copyrighted content, impersonation, investment scam, lost asset, phishing, seed phrase harvesting, tm advertisement, impersonating Trezor

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

trezor.io-start.app

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 3 det. ChainPatrol ChainAbuse 3 reports URLQuery SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Third-Party Detection — ChainAbuse
3 reports filed for trezor.io-start.app · category: Impersonation · source checked
Flagged by automated brand-abuse detection · Nov 6, 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
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

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.io-start.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

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 →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Request a correction or appeal How PhishDestroy works
Embed this reportA 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.io-start.app"
  title="PhishDestroy threat report for trezor.io-start.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>