Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 12/92 engines flagged. malicious: 12. suspicious: 0. Analysis time (as stored): 2026-10-13T09:38:59Z. Retrieved (as stored): 2026-11-08T15:58:34Z. 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-bridge-cdn.vercel.app favicon

trezor-bridge-cdn.vercel.app

In short

PhishDestroy first recorded trezor-bridge-cdn.vercel.app on 2026-11-08. Stored VirusTotal result: 12/92 engines flagged. malicious: 12. suspicious: 0. Analysis time (as stored): 2026-10-13T09:38:59Z. Retrieved (as stored): 2026-11-08T15:58:34Z.

“Trézór Bridge® |™ -(en-us)”

Review the evidence
Registrar
United StatesVercel
Resolved IP
United States216.198.79.67Amazon.com, Inc. · CDN
First observed
Nov 8, 2026
PhishDestroy assessment Critical
96/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 12/92
VirusTotal
12 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 99
Cloudflare Radar
Phishing
Page captures
5
open gallery
Nov 8, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded trezor-bridge-cdn.vercel.app on 2026-11-08. Stored VirusTotal result: 12/92 engines flagged. malicious: 12. suspicious: 0. Analysis time (as stored): 2026-10-13T09:38:59Z. Retrieved (as stored): 2026-11-08T15:58:34Z. Risk: critical (96/100). Registrar: Vercel. Status: Last known active. Hosting: Amazon.com, Inc. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
12 / 92
Hosting
United States216.198.79.67Amazon.com, Inc. · CDN
Registrar
United StatesVercel
Page captures
5
Page captures Source results Registration record

Recorded source summary

PhishDestroy stores a record for trezor-bridge-cdn.vercel.app. Source observations are dated separately; missing checks do not establish safety.

A reviewed analysis is not available for this text revision. Consult the dated source records below.

Source evidenceVirusTotal 12 / 92 6 sources

VirusTotal

12 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
48
Malicious
12
Suspicious
0
Undetected
32

Vendor labels

DNS8
phishing
ESET
phishing
VIPRE
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
SOCRadar
phishing
ADMINUSLabs
malicious
BitDefender
phishing
alphaMountain.ai
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

Tucows Domains Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    216.198.79.67
  • TTL, seconds
    300
    Type
    A
    Value
    64.29.17.67

DNS records observed

JARM fingerprint

3fd3fd00000000000043d43d00043dc3b2afa8a5ec09b510a8559aff7899fb

Certificate

Subject alternative names
  • *.vercel.app
Issuer
Google Trust Services / WR1
Serial
f7911168ffa7d0f4135e24792e7a52a8
SHA-256
8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093
Subject
*.vercel.app
Valid until
Valid from

Registration record

Registrar
Tucows Domains Inc
Registrar IANA ID
69
Registrar URL
http://www.tucows.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • ns1.vercel-dns-3.com
  • ns2.vercel-dns-3.com
  • ns3.vercel-dns-3.com
  • ns4.vercel-dns-3.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 48,
    "malicious": 12,
    "suspicious": 0,
    "undetected": 32
}
Vendor labels
{
    "DNS8": "phishing",
    "ESET": "phishing",
    "VIPRE": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "ADMINUSLabs": "malicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
Tucows Domains Inc
Created
2020-01-28T03:03:04Z
Expires
2026-01-28T03:03:04Z
Updated
2025-01-26T03:25:55Z
First seen
2025-10-21T21:57:34Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "216.198.79.67"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "64.29.17.67"
    }
]
Dns at
2026-10-13T09:45:21Z
Jarm
3fd3fd00000000000043d43d00043dc3b2afa8a5ec09b510a8559aff7899fb
Certificate
{
    "san": [
        "*.vercel.app"
    ],
    "issuer": "Google Trust Services / WR1",
    "serial": "f7911168ffa7d0f4135e24792e7a52a8",
    "sha256": "8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093",
    "subject": "*.vercel.app",
    "valid_to": "2026-11-27T19:48:08Z",
    "valid_from": "2026-08-29T19:48:09Z"
}
Registration record
{
    "registrar": "Tucows Domains Inc",
    "registrar_iana_id": "69",
    "registrar_url": "http://www.tucows.com",
    "created": "2020-01-28T03:03:04Z",
    "updated": "2025-01-26T03:25:55Z",
    "expires": "2026-01-28T03:03:04Z",
    "status": [
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "ns1.vercel-dns-3.com",
        "ns2.vercel-dns-3.com",
        "ns3.vercel-dns-3.com",
        "ns4.vercel-dns-3.com"
    ],
    "dnssec": "unsigned"
}
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
12
denominator
92
malicious
null
suspicious
null
vendors
["ADMINUSLabs","alphaMountain.ai","BitDefender","CyRadar","DNS8","ESET","Fortinet","Lionic","SOCRadar","Sophos","VIPRE","Webroot"]
observed_at
2026-10-13 09:38:59
checked_at
2026-11-08 16:58:34
fetched_at
2026-11-08 15:58:35
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

de5194a4-2944-4353-a571-e045a54d32c3

Final URL

https://trezor-bridge-cdn.vercel.app/

HTTP response

200

Navigation history

  • URL
    https://trezor-bridge-cdn.vercel.app/
    Status
    200

DOM structure hash

ac659fc233d472156d4ef06a6babd111990733edc17b1e9e008511bd34a727ed

Document hash

27b09f7052b889b5ee076b62ba766480f941f1d2b05492c69a3a493896e05908

Phishing classifier result

  • phishing

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    trezor-bridge-cdn.vercel.app
    Type
    A
    Value
    216.198.79.3
  • Name
    trezor-bridge-cdn.vercel.app
    Type
    A
    Value
    64.29.17.3

DNSSEC valid

No

IP address

127.0.1.27

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

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
Tucows Domains Inc
Registered
Updated
Expires
Nameservers
  • ns1.vercel-dns-3.com
  • ns2.vercel-dns-3.com
  • ns3.vercel-dns-3.com
  • ns4.vercel-dns-3.com
Original source fields · JSON
Uuid
de5194a4-2944-4353-a571-e045a54d32c3
Final url
https://trezor-bridge-cdn.vercel.app/
Status
200
History
[
    {
        "url": "https://trezor-bridge-cdn.vercel.app/",
        "status": 200
    }
]
DOM structure hash
ac659fc233d472156d4ef06a6babd111990733edc17b1e9e008511bd34a727ed
Document hash
27b09f7052b889b5ee076b62ba766480f941f1d2b05492c69a3a493896e05908
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "trezor-bridge-cdn.vercel.app",
        "type": "A",
        "value": "216.198.79.3"
    },
    {
        "name": "trezor-bridge-cdn.vercel.app",
        "type": "A",
        "value": "64.29.17.3"
    }
]
Dnssec valid
false
Ip
127.0.1.27

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

Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "Tucows Domains Inc",
    "created": "2020-01-28T03:03:04Z",
    "updated": "2026-03-14T03:03:04Z",
    "expires": "2036-01-28T03:03:04Z",
    "nameservers": [
        "ns1.vercel-dns-3.com",
        "ns2.vercel-dns-3.com",
        "ns3.vercel-dns-3.com",
        "ns4.vercel-dns-3.com"
    ]
}
Separate stored summary: Not recorded · 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
null
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.

URLScan

Malicious · engine verdict · score 99

SHA-256 27b09f7052b889b5ee076b62ba766480f941f1d2b05492c69a3a493896e05908

Open report
URLScanOriginal source recordObserved: 18 fields

Observed: · Retrieved:

Report ID

01a1bbf2-77b4-73a7-a02c-1ba23c9a1a1f

Final URL

https://trezor-bridge-cdn.vercel.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://trezor-bridge-cdn.vercel.app/
    From
    http://trezor-bridge-cdn.vercel.app/
    Status
    307

IP address

216.198.79.195

Contacted IP addresses

  • 216.198.79.195

Autonomous systems (ASN)

  • 16509

Server countries

  • US

Document hash

27b09f7052b889b5ee076b62ba766480f941f1d2b05492c69a3a493896e05908

TLS session and certificate

Subject alternative names
  • *.vercel.app
Cipher
AES_128_GCM
Issuer
WR1
Subject
*.vercel.app
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

382

Registered domain age, days

382

Certificate age, days

8

Certificate validity, days

89

Page requests

2

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-2aab354
Score
99
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
Vercel
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=63072000; includeSubDomains; preload
Original source fields · JSON
Uuid
01a1bbf2-77b4-73a7-a02c-1ba23c9a1a1f
Final url
https://trezor-bridge-cdn.vercel.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://trezor-bridge-cdn.vercel.app/",
        "from": "http://trezor-bridge-cdn.vercel.app/",
        "status": 307
    }
]
Ip
216.198.79.195
Contacted IP addresses
[
    "216.198.79.195"
]
Asns
[
    "16509"
]
Countries
[
    "US"
]
Document hash
27b09f7052b889b5ee076b62ba766480f941f1d2b05492c69a3a493896e05908
Tls
{
    "san": [
        "*.vercel.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR1",
    "subject": "*.vercel.app",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-29T11:46:09Z",
    "valid_from": "2026-10-31T11:46:10Z"
}
Domain age days
382
Apex age days
382
Tls age days
8
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-2aab354"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "Vercel",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=63072000; includeSubDomains; preload"
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
01a165e8-d635-74b5-a1e7-978659352d00
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

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: 22 fields

Mail configuration

SPF lookups
0

CAA records

Count
2
Domain
vercel.app
Allowed issuers
  • pki.goog
  • letsencrypt.org

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Page title and metadata

Page title
Trézór Bridge® |™ -(en-us)
Description
Trézór Bridge® |™ - The next-generation cryptographic bridge solution for secure digital asset transfers between blockchain networks.

Trackers

Requests
1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
4
TLS
14
Waiting
18
Connection
6
Download
1
Response time, ms
43

TLS connection

ALPN
h2
Cipher
TLS_AES_128_GCM_SHA256
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
13207
CO₂, grams
0.0005
Cleaner than, %
66

DNS servers

Nameservers
  • IP address
    205.251.199.60
    Host
    ns4.vercel-dns-3.com
  • IP address
    205.251.193.92
    Host
    ns1.vercel-dns-3.com
  • IP address
    205.251.194.149
    Host
    ns2.vercel-dns-3.com
  • IP address
    205.251.197.116
    Host
    ns3.vercel-dns-3.com
DNS zone
vercel.app

Location

IP address
216.198.79.195
ASN
16509
Organization
Amazon.com, Inc.
City
Walnut
Country
US

TLS certificate

Issuer
Google Trust Services / WR1
Subject
*.vercel.app

DNS records

A
  • 216.198.79.195
  • 64.29.17.195

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=63072000; includeSubDomains; preload
Observation
Site is compatible with the HSTS preload list!
Preload compatible
Yes

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
64.29.17.195
IP version
4

Redirects

Redirect chain
  • https://trezor-bridge-cdn.vercel.app

Technology stack

Technologies
  • Vercel
  • HSTS

Page links

Internal links
5

HTTP headers

Response headers
Server
Vercel
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=63072000; includeSubDomains; preload
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 2,
    "domain": "vercel.app",
    "issuers": [
        "pki.goog",
        "letsencrypt.org"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Page title and metadata
{
    "title": "Trézór Bridge® |™ -(en-us)",
    "description": "Trézór Bridge® |™ - The next-generation cryptographic bridge solution for secure digital asset transfers between blockchain networks."
}
Trackers
{
    "requests": 1
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 4,
        "tls": 14,
        "wait": 18,
        "connect": 6,
        "download": 1
    },
    "response_ms": 43
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 13207,
    "co2_grams": 0.0005,
    "cleaner_than": 66
}
Dns server
{
    "ns": [
        {
            "ip": "205.251.199.60",
            "host": "ns4.vercel-dns-3.com"
        },
        {
            "ip": "205.251.193.92",
            "host": "ns1.vercel-dns-3.com"
        },
        {
            "ip": "205.251.194.149",
            "host": "ns2.vercel-dns-3.com"
        },
        {
            "ip": "205.251.197.116",
            "host": "ns3.vercel-dns-3.com"
        }
    ],
    "zone": "vercel.app"
}
Location
{
    "ip": "216.198.79.195",
    "asn": "16509",
    "org": "Amazon.com, Inc.",
    "city": "Walnut",
    "country": "US"
}
Ssl
{
    "issuer": "Google Trust Services / WR1",
    "subject": "*.vercel.app"
}
DNS records
{
    "A": [
        "216.198.79.195",
        "64.29.17.195"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=63072000; includeSubDomains; preload",
    "message": "Site is compatible with the HSTS preload list!",
    "compatible": true
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=63072000; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "64.29.17.195",
    "family": 4
}
Redirects
{
    "chain": [
        "https://trezor-bridge-cdn.vercel.app"
    ]
}
Tech stack
{
    "technologies": [
        "Vercel",
        "HSTS"
    ]
}
Page links
{
    "internal_count": 5
}
HTTP headers
{
    "headers": {
        "server": "Vercel",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=63072000; includeSubDomains; preload"
    }
}

Questions about trezor-bridge-cdn.vercel.app

Is trezor-bridge-cdn.vercel.app legit?

PhishDestroy rates trezor-bridge-cdn.vercel.app as critical risk (96/100) from the recorded evidence; it was first recorded on 2026-11-08. Stored VirusTotal result: 12/92 engines flagged. malicious: 12. suspicious: 0. Analysis time (as stored): 2026-10-13T09:38:59Z. Retrieved (as stored): 2026-11-08T15:58:34Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is trezor-bridge-cdn.vercel.app safe to connect a wallet?

This report does not record which wallet requests trezor-bridge-cdn.vercel.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-bridge-cdn.vercel.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 · 5 captures

URLScan · 2026-11-08 1 / 5
SourceURLScan · 2026-11-08
Recorded
StateStored capture
HTTP status200
Final URLhttps://trezor-bridge-cdn.vercel.app/
Position1 / 5
Open capture Source Report Wayback Download
All capture links and hashes (5)

Domain details

Domain
IP Context United States216.198.79.67 Vercel shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Vercel US(US)
Abuse contactabuse@vercel.com
Hosting abuse contact abuse@vercel.com Amazon.com, Inc. · AS16509
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedNov 8, 2026
Submitted URLhttp://trezor-bridge-cdn.vercel.app/
Observed page title
Trézór Bridge® |™ -(en-us)
TLS Certificate
Issued by WR1 · stored validity ends in 19 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States216.198.79.67
Network ASN
AS16509
Organization
Amazon.com, Inc.
Observed location
United StatesWalnut, US
Server header
Vercel

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
WR1
Valid from
2026-08-29 19:48:09
Valid until
2026-11-27 19:48:08
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093
Certificate names · 1 SAN
  • *.vercel.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 · 216.198.79.67rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

12 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
DNS8
ESET
VIPRE
Lionic
Sophos
CyRadar
Webroot
Fortinet
SOCRadar
ADMINUSLabs
BitDefender
alphaMountain.ai

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of trezor-bridge-cdn.vercel.app · checked Nov 8, 2026

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

Captured network requests

Network requests: 2 SHA-256 hashes: 2 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-08 16:18 UTC.

Open this scan on URLScan 01a1bbf2-77b4-73a7-a02c-1ba23c9a1a1f ↗

All retained availability observations1

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_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-08 16:28:35.541533
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 9. 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-bridge-cdn.vercel.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Automated brand label: Trezor · Forensic Evidence Collected Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 99
  • 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: 12/92
  • Automated brand label: Trezor
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
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

5 entries
  1. URLScan

    Page captured

    View source
  2. Wayback Machine

    Page archived

    View source
  3. Cloudflare Radar

    Phishing

    View source
  4. Added to PhishDestroy

    trezor-bridge-cdn.vercel.app

    View source
  5. VirusTotal

    12/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

1 community report

CategoryPhishing

The PhishFort Detection System has flagged this as a domain threat, classified as infringement. Threat detected at 2025-10-21T20:18:37.578Z.

Check for cloaking

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

trezor-bridge-cdn.vercel.app

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 12 det. ChainPatrol ChainAbuse 1 report URLQuery SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Third-Party Detection — ChainAbuse
1 report filed for trezor-bridge-cdn.vercel.app · category: Phishing · source checked
Flagged by PhishFort Detection System · Oct 21, 2025 — 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-bridge-cdn.vercel.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.

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-bridge-cdn.vercel.app"
  title="PhishDestroy threat report for trezor-bridge-cdn.vercel.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>