Skip to security report
Domain security and threat intelligence
trezor.wallet.org.ph favicon

trezor.wallet.org.ph

In short

trezor.wallet.org.ph is a Trezor impersonation page detected by PhishDestroy on 2026-08-25. Risk: critical (88/100). Status: Reachable · access restricted. Hosting: Cloudflare, Inc. VirusTotal: 10/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

“Attention Required! | Cloudflare”

Resolved IP
104.26.9.49
PhishDestroy assessment Critical
Availability Reachable · access restricted Reachable response; page content was not verified Observed · HTTP probe
VirusTotal detections: 10/92 Spamhaus DBL: DBL_PHISH Automated brand label: Trezor Last known active
Aug 25, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 10. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Source evidenceVirusTotal 10 / 92 6 sources

VirusTotal

10 / 92 engine detections

Open report

Spamhaus DBL

DBL_PHISH

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

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

Analysis

Critical
VirusTotal
10 / 92
Page captures
2

PhishDestroy threat report

Overview

trezor.wallet.org.ph is an impersonation phishing site that uses the Trezor brand to target owners of Trezor hardware wallets. It puts the brand name at the front of a Philippine wallet.org.ph address, so a hurried reader sees "trezor" and "wallet" and assumes it is official. PhishDestroy first flagged it on 2026-08-25, and it was still online on 2026-10-19, with its content served behind a protection layer.

How the scam works

Fake Trezor pages usually claim the device needs a firmware update, a security check or a wallet "recovery." They then ask the victim to type the 12- or 24-word recovery seed into a web form. Whoever holds that seed controls the wallet, so the attacker can rebuild it elsewhere and empty it without ever touching the physical device. The page title currently reads "Attention Required! | Cloudflare," which is a Cloudflare challenge screen rather than Trezor branding, while we classify the site as Trezor impersonation.

Evidence

On 2026-10-07, 10 of 92 VirusTotal engines flagged the domain. Detections came from alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data and PhishFort. PhishFort specializes in crypto-brand protection, so its verdict carries particular weight here. Spamhaus lists the domain in its DBL with the DBL_PHISH tag, which mail filters and DNS resolvers use to block it, and it is on the PhishDestroy blocklist.

Infrastructure

The site resolves to 104.26.9.49 on Cloudflare's network, geolocated to Canada. That means the address belongs to Cloudflare's shared front end, not to whoever actually runs the page. Its HTTPS certificate comes from Google Trust Services (WE1), the routine automated certificate for this kind of setup. The padlock in the browser says nothing about whether the site is genuine.

What to do

Trezor never asks for your recovery seed on a website, in an app form or by message. If you typed your seed into this site, treat the wallet as compromised. Set up your Trezor again with a freshly generated seed and move all funds to the new addresses immediately. If you downloaded any "Trezor" software from this domain, remove it and scan the machine. Defenders should block the hostname at the DNS, proxy and mail layers, and report it to Cloudflare and Trezor's security team.

Collected source details

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

URLScan · 2026-08-25T08:59:57Z

Observed: · Retrieved:

Uuid
01a03825-b803-72b8-8f1f-597cb1ccded2
Final url
https://trezor.wallet.org.ph/
Status
403
Ip
172.67.74.162
Contacted IP addresses
[
    "172.67.74.162"
]
Asns
[
    "13335"
]
Linked domains
[
    "www.cloudflare.com"
]
Document hash
1964624430ec55ef357ec38161c46adfd953173e3706214e1c94e193b125c55c
Script hashes
[
    "4e4a845231637906eae640214acce62f08e845c97b3d0d8823ed7eef5358cb30"
]
Globals
[
    "_cf_translation"
]
Cookies
[
    "cf_clearance"
]
Tls
{
    "san": [
        "wallet.org.ph",
        "*.wallet.org.ph"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "wallet.org.ph",
    "protocol": "TLS 1.3",
    "valid_to": "2026-10-01T06:07:54Z",
    "valid_from": "2026-07-03T05:07:58Z"
}
Domain age days
53
Apex age days
74
Tls age days
53
Tls valid days
90
Requests
7
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 64,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=UTF-8",
    "x-frame-options": "SAMEORIGIN",
    "referrer-policy": "same-origin"
}
Cloudflare Radar · 2026-08-25T16:01:47Z

Observed: · Retrieved:

Uuid
f6d7234f-a921-4348-b68d-f5687b8cad9a
Final url
https://trezor.wallet.org.ph/
Status
403
Redirected
https-only
History
[
    {
        "url": "http://trezor.wallet.org.ph/",
        "status": 307
    },
    {
        "url": "https://trezor.wallet.org.ph/",
        "status": 403
    }
]
DOM structure hash
e1e0ec04ba2dccd9143717ccf431a0c9d267fac4083951806a2652b5fb5fcf8d
Document hash
d7b615dcc6a766eba0064deb5585a1e162def32682f900db43c83f6278f4e12a
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "trezor.wallet.org.ph",
        "type": "A",
        "value": "104.26.9.49"
    },
    {
        "name": "trezor.wallet.org.ph",
        "type": "A",
        "value": "104.26.8.49"
    },
    {
        "name": "trezor.wallet.org.ph",
        "type": "A",
        "value": "172.67.74.162"
    },
    {
        "name": "trezor.wallet.org.ph",
        "type": "AAAA",
        "value": "2606:4700:20::681a:931"
    },
    {
        "name": "trezor.wallet.org.ph",
        "type": "AAAA",
        "value": "2606:4700:20::681a:831"
    },
    {
        "name": "trezor.wallet.org.ph",
        "type": "AAAA",
        "value": "2606:4700:20::ac43:4aa2"
    }
]
Dnssec valid
false
Ip
104.26.9.49

Questions about trezor.wallet.org.ph

Is trezor.wallet.org.ph legit?

No. PhishDestroy classifies trezor.wallet.org.ph as a Trezor impersonation page (risk: critical, 88/100); it was first detected on 2026-08-25. VirusTotal: 10/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is trezor.wallet.org.ph safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on trezor.wallet.org.ph. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used trezor.wallet.org.ph?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 2 captures

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
HTTP Status403 Forbidden
Technical detailsProvenance & timestamps
First DetectedAug 25, 2026
DOM Analysisanalyzed Oct 9, 2026score 88/100
Submitted URLhttps://trezor.wallet.org.ph/?… query redacted
Favicon Hash
Observed page title
Attention Required! | Cloudflare
TLS Certificate
Issued by Google Trust Services · stored validity ends in 32 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.26.9.49
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services
Valid from
2026-08-31 05:29:26
Valid until
2026-11-29 06:29:24
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-09 13:03:12 UTC
Collection source
PhishDestroy collector
Certificate fingerprint96b738e341cc9b3b7c7c4797648c09995c9c2c0e78435a43a197a5935575b96e
Certificate names · 1 SAN
  • wallet.org.ph

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

Latest Classified Outcome 2026-10-22 10:33:55 UTC

Primary outcome Reachable but protected reason: Cloudflare Challenge 85% confidence
Attribution Cloudflare mechanism: Challenge source: Current Http Probe
Evidence layers Availability: Reachable but protected Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Reachable but protected Cloudflare Challenge Cloudflare Challenge 85% 2026-10-22 10:33:55 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:33:55 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 · 1 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

10 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 11 detections
alphaMountain.ai
BitDefender
CRDF
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
PhishFort
SOCRadar
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of trezor.wallet.org.ph · checked Aug 25, 2026

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

Availability observations

Last reachable 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.

Stored observation history20

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  2. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  3. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  4. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  5. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

Earlier observations 15
  1. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  2. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  3. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  4. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  5. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  6. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  7. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  8. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  9. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  10. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  11. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  12. Availability monitor · Recorded state

    protected

    cloudflare_challenge · Cloudflare · challenge

  13. VirusTotal · Detection count

    5→6

  14. VirusTotal · Detection count

    4→5

  15. VirusTotal · Detection count

    3→4

Recorded activity

3 entries
  1. VirusTotal

    10/92 engine detections

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. Added to PhishDestroy

    trezor.wallet.org.ph

    View source

Lookalike domains

74 stored lookalike domains

Show all (62)
grezor.io replacement rezor.io omission rrezor.io replacement rtezor.io transposition tdezor.io replacement teezor.io replacement terzor.io transposition tezor.io omission tfezor.io replacement tr.ezor.io subdomain tr3zor.io replacement treeor.io replacement treezor.io insertion treor.io omission treqor.io replacement tresor.io replacement trezeor.io insertion trezer.io vowel-swap trezior.io insertion trezir.io replacement trezkor.io insertion trezlor.io insertion trezo.io omission trezoe.io replacement trezoir.io insertion trezopr.io insertion trezor-io.com various trezorio.com various trezot.io replacement trezpor.io insertion trezpr.io replacement trezr.io omission trezro.io transposition trezxor.io insertion trezzor.io insertion trizor.io vowel-swap trozor.io vowel-swap trrzor.io replacement trtezor.io insertion trwezor.io insertion trwzor.io replacement trzeor.io transposition trzzor.io replacement ttezor.io replacement ttrezor.io insertion tyrezor.io insertion yrezor.io replacement ytrezor.io insertion prezor.io bitsquatting treazor.io insertion trerzor.io insertion trewzor.io insertion trexor.io bitsquatting trez0r.io homoglyph trezaor.io insertion trezora.io addition trezore.io addition trezoro.io addition trezorr.io addition trezors.io addition xn--tezor-5bb.io homoglyph xn--trezo-9bb.io homoglyph

Community intelligence

1 community report

CategoryIMPERSONATION

Phishing: impersonation, impersonating Trezor

Check for cloaking

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

trezor.wallet.org.ph

Evidence & External Reports

Community Scam Report — ChainAbuse
1 report filed for trezor.wallet.org.ph (1 written by a person) · category: Impersonation · source checked
“Phishing: impersonation, impersonating Trezor”
— reported by Anonymous Trusted reporter on Aug 25, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked 0 stored notification records Reachable · access restricted

Listed domains receive at least one abuse report; this entry has no retained notification history.

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

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

Official reporting routes

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

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

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

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

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

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

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including trezor.wallet.org.ph)
  • 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

Stay Informed, Stay Safe

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

Live Threat Feed Appeal This Listing
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.

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.wallet.org.ph"
  title="PhishDestroy threat report for trezor.wallet.org.ph"
  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>