Lompat ke laporan keamanan
Dasbor Analitik
Keamanan domain dan intelijen ancaman
trezorsafety.io favicon

trezorsafety.io

“trezorsafety.io”

Registrar
NETIM SAS
Resolved IP
172.67.196.189
Registered
17/10/2026
PhishDestroy assessment Kritis
Ketersediaan Terakhir diketahui aktif Pengamatan keterjangkauan tersimpan terbaru Teramati · HTTP probe
Sinyal risiko
Daftar blokir yang disimpan cocok: 2 Label merek otomatis: Trezor Domain muda: 3 berumur hari
20/10/2026 CDN
API
Domain ini telah ditandai sebagai berbahaya
Daftar blokir publik yang melaporkan kecocokan: 2. Berhati-hatilah — jangan memasukkan kredensial atau informasi pribadi.
VirusTotal
0 / 92
engine detections
Google Safe Browsing
No threat flag
Page captures
2
open gallery
Domain age
3 days
Ringkasan laporan

Peniruan Trezor: trezorsafety.io — Terakhir diketahui aktif (HTTP 200). Ringkasan bukti: VirusTotal 0/92; 2 external blocklist matches (MetaMask, SEAL)…

Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.

Source evidenceVirusTotal 0 / 92 5 sources

VirusTotal

0 / 92 engine detections

Buka laporan

Google Safe Browsing

No threat flag

Buka laporan

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

Analysis

Kritis
VirusTotal
0 / 92
Page captures
2
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy has listed trezorsafety.io as a suspicious domain. The domain was first observed by PhishDestroy on 2026-10-20.

How the scam works

The current listing does not identify a specific malicious technique; it only indicates that the domain is considered suspicious. In general, such domains can be used to lure users into revealing credentials, installing malware, or interacting with fraudulent services.

Evidence

VirusTotal scanned the site on 2026-10-19 and reported 0 detections out of 92 engines. Google Safe Browsing checked the URL on 2026-10-20 and did not flag it. External blocklists MetaMask and SEAL listed the domain on 2026-10-20, and PhishDestroy’s internal blocklist also marked it as suspicious on the same date. OTX recorded zero pulses for the domain on 2026-10-20.

Infrastructure

The recorded IP address for trezorsafety.io was 172.67.196.189 as of 2026-10-20. No additional registration or hosting details are available in the current evidence.

What to do

If you visited the site but did not submit any credentials, no immediate action is required beyond normal vigilance. If you entered login information, passwords, or other sensitive data, change those credentials promptly and monitor associated accounts for unusual activity. Defenders should add a rule to block traffic to trezorsafety.io and review logs for any connections to 172.67.196.189.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Terdaftar View source
PhishDestroy PhishDestroy list View source
SEAL Terdaftar View source

Last checked

Tangkapan tersimpan · 2 captures

Primary capture 1 / 2
SumberPrimary capture
Recorded2026-10-20 13:11 UTC
StateStored capture
HTTP status at archiveHTTP 200
Final URLhttps://trezorsafety.io/
Position1 / 2
Open capture Wayback Unduh

Domain details

Domain
URLScan verdict Analisis selesai score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Reputasi Edge-IP tidak dikaitkan dengan domain ini.
Registrar NETIM SAS
Pendaftar ICANNICANN Lookup (RDAP) →
Pencarian WHOISICANN RDAP untuk trezorsafety.io →
PendaftaranDibuat 17/10/2026 (3d · Brand New!) — Expires 17/10/2027
Status HTTP200
Detail teknisProvenance & timestamps
Pertama Kali Terdeteksi20/10/2026
DOM Analysisanalyzed 20/10/2026score 80/100
Submitted URLhttp://trezorsafety.io/
Favicon Hash
Observed page title
trezorsafety.io
Sertifikat TLS
Diterbitkan oleh Let's Encrypt / YE2 · stored validity ends in 86 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.67.196.189
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

Reputasi Edge-IP tidak dikaitkan dengan domain ini.

Server nama 1

  • ezra.ns.cloudflare.com

Mail routing 2 MX records

  • mx2.netim.netpriority 10
  • mx1.netim.netpriority 10

Location describes the IP network.

Sertifikat TLS

Issuer
Let's Encrypt / YE2
Valid from
2026-10-17 23:27:40
Valid until
2027-01-15 23:27:39
Validity
Within stored validity dates
Collection time
2026-10-20 22:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprintaa93148a4df1ba418e2931e69a05a594c0656c56f26bcec674d470900476f8c9

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

viewdns.info · 172.67.196.189rapiddns.io

Latest Classified Outcome 2026-10-21 01:58:15 UTC

Primary outcome Konten aktif 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 Konten aktif Ordinary HTTP content served 90% 2026-10-21 01:58:15 UTC
RDAP registration Tidak diketahui
Observed timeline last reachable: 2026-10-21 01:58:15 UTC last content: 2026-10-21 01:58:15 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.
Teknologi · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Laporkan Domain Ini Kirimkan bukti & bantu lindungi orang lain

Bukti Terarsip

Wayback Machine Snapshot
Cuplikan sejarah tersedia untuk tinjauan bukti
View Archive
Analisis Performa Situs

Google PageSpeed Insights — mobile performance audit of trezorsafety.io · checked Oct 20, 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
0.91s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://trezorsafety.io/
Final URL: https://trezorsafety.io/
trezorsafety.io
Respons
HTTP 200
HTML body
4.9 KB
Compressed
1.5 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
Server: cloudflare
X-Powered-By: PHP/8.5.4
Cache-Control: no-store, no-cache, must-revalidate
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 15
alt-svc
h3=":443"; ma=86400
Cache-Control
no-store, no-cache, must-revalidate
cf-cache-status
DYNAMIC
CF-RAY
a4d84ba3d92bd396-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Tue, 20 Oct 2026 13:16:10 GMT
Host
trezorsafety.io
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=OEQjSOla5YU3va9Xyne4Lntb5AQd1JhSJRMk2899jWnQCNb4JX0a4HF3DcoOsLRibfrUcxlpLGPazDqfv%2BlUE7Xz1vfN%2F8xcSrV%2BB2VqKP46cixfl0jUGpVUQ%2FkE0J%2BGB48%3
Server
cloudflare
Transfer-Encoding
chunked
Vary
accept-encoding
X-Powered-By
PHP/8.5.4

Values retained by the collector; long values may be shortened during collection.

Archived
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.

Stored observation history1

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

    Tidak diketahui→live_content

    content_served

Recorded activity

3 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    0/92 engine detections

    View source
  3. Added to PhishDestroy

    trezorsafety.io

    View source

Domain serupa

74 domain serupa tersimpan

treaor.io replacement Laporan internal treozr.io transposition Laporan internal trzezor.io insertion Laporan internal trzor.io omission Laporan internal rtrezor.io insertion Laporan internal terezor.io insertion Laporan internal trazor.io bitsquatting Laporan internal trexzor.io insertion Laporan internal trezort.io addition Laporan internal 5rezor.io replacement 6rezor.io replacement frezor.io replacement
Tampilkan semua (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

Check for cloaking

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

trezorsafety.io

Bukti & Laporan Eksternal

Analisis Keamanan
URLScan Analyzed VirusTotal ChainPatrol URLQuery SSL Laboratorium CF Radar Buka laporan WOT ScamAdviser Pemeriksa Daftar Hitam URLVoid Sucuri SiteCheck Observatorium MDN
OSINT & Intelijen
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Batu Hudson Sign-in search IntelX crt.sh Sertifikat WHOIS Wayback Archived
DNS & Jaringan
nslookup.io DNS bgp.tools ASN /Rute
SEO & Domain
SpyFu Moz DA/PA Ahrefs Tautan balik
Analisis Mendalam
Analisis Mendalam
Help & reporting

Apakah Anda Terpengaruh oleh Situs Ini?

2 evidence signal groups linked 0 stored notification records Terakhir diketahui aktif

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.

Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Bukan laporan penegakan hukum
Banding atas Nama Domain
Minta peninjauan jika Anda pemilik domain ini dan yakin cantumannya salah
Waspadalah terhadap penipu yang mengatasnamakan pemulihan! Penjahat dapat menghubungi korban lagi sambil berpura-pura menjadi penyelidik, pengacara, atau agen pemulihan. Jangan membayar biaya di muka atau membagikan kredensial. Pelajari lebih lanjut tentang penipuan dalam proses pemulihan →

Laporkan kepada Pihak Berwenang di Daerah Anda

Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.

Direktori 97 negara

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

Draf yang dibantu AI — detail insiden diproses oleh penyedia AI · Tinjau dan kirimkan sendiri
After a phishing incident

Rekomendasi & Saran bagi Para Korban

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

Apa yang harus saya lakukan segera?

Mendesak

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

  • Ubah semua kata sandi — email, akun Exchange, apa pun yang menggunakan kata sandi yang sama
  • Aktifkan 2FA menggunakan aplikasi otentikator (bukan SMS). Nonaktifkan pemulihan berbasis SMS
  • Kartu pembeku jika Anda telah memasukkan detail perbankan di situs phishing tersebut

Informasi apa saja yang sebaiknya saya kumpulkan untuk laporan saya?

Pedoman FBI

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.
  • Tanggal dan waktu yang tepat — dari setiap transaksi dan kontak pertama dengan penipu
  • Tangkapan layar — situs web penipuan, pesan obrolan, email, transaksi dompet digital, media sosial
  • Semua URL & domain digunakan oleh penipu (termasuk trezorsafety.io)
  • Komunikasi — email, pesan teks, nomor telepon, dan nama pengguna yang digunakan oleh penipu tersebut

Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.

Ke mana saya harus melaporkan penipuan ini?

  • FBI IC3 — Pusat Pengaduan Kejahatan Internet (Laporan tingkat federal AS)
  • Europol — Pelaporan kejahatan siber di Eropa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Polisi setempat — membuat catatan resmi, meskipun mereka tidak dapat bertindak segera

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?

  • Situs web palsu — salinan yang persis sama dengan situs asli, dengan domain yang sedikit diubah
  • Pemotongan babi — kepercayaan yang dibangun selama beberapa minggu melalui Telegram/WhatsApp/aplikasi kencan, lalu uangnya dicuri
  • Penipuan pemulihan — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Penipuan yang didukung oleh kecerdasan buatan — deepfakes, serangan phishing otomatis, dan situs yang dihasilkan oleh kecerdasan buatan (AI) yang membuat penipuan semakin sulit dideteksi

Bagaimana cara saya melindungi diri di masa depan?

  • Tandai situs resmi — jangan pernah mengklik tautan dari email, pesan langsung (DM), atau iklan
  • Memverifikasi domain — periksa PhishDestroy Sebelum berinteraksi. Periksa HTTPS, ejaan, dan usia domain
  • "Terlalu bagus untuk jadi kenyataan" = penipuan — imbal hasil yang dijamin, dukungan dari selebriti, tenggat waktu yang mendesak

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

Periksa Domain Apa Pun

Analisis ancaman menggunakan daftar blokir yang disimpan, WHOIS, DNS, dan bukti pemindaian publik

Pindai Sekarang

Laporkan Phishing

Laporkan domain yang mencurigakan ke basis data ancaman kami — lindungi komunitas

Laporan

Pemberitahuan Ancaman Real-Time

Laporan phishing terbaru dan perubahan ketersediaan yang diamati

Pantau

Tetap Terinformasi, Tetap Aman

Pantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive

Pemberitahuan Ancaman Real-Time Ajukan Banding Terhadap Iklan Ini
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

Sematkan Laporan Ini

Bagikan informasi ancaman ini di situs web atau blog Anda

embed.html 
<iframe
  src="https://phishdestroy.io/id/embed/domain/trezorsafety.io"
  title="PhishDestroy threat report for trezorsafety.io"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>