VirusTotal
14 / 89 engine detections
Raporu açGoogle taklidi: trezou-iostre-us.netlify.app — İçerik kullanılamıyor (HTTP 404). Kanıt özeti: VirusTotal 14/89 (alphaMountain.ai, BitDefender, ESET, Emsisoft…
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
14 / 89 engine detections
Raporu açZararlı
Raporu açThreat flag recorded
Raporu açno community references
Raporu açResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
trezou-iostre-us.netlify.app is an impersonation phishing page on a free Netlify subdomain. Its jumbled, official-sounding name is built to pass a quick glance in a search result or chat link. PhishDestroy first saw it on 2026-09-05. The site went offline on 2026-09-15, and on 2026-10-19 the root still served no content.
Impersonation pages copy the look of a real service so visitors trust the form in front of them. A victim arriving from an ad, message or search result is asked to sign in, verify an account or restore access. On crypto-themed pages that often means typing a wallet recovery phrase or private key. Whatever is entered goes straight to the operators, who can then take over the account or empty the wallet.
Fourteen of 89 VirusTotal engines flagged the site as of 2026-09-17, including BitDefender, ESET, Kaspersky, Fortinet, Emsisoft, G-Data, alphaMountain.ai and Google Safe Browsing. That is a modest share of engines, but it spans several major vendors working independently. Google Safe Browsing classifies the site as SOCIAL_ENGINEERING, so Chrome and other browsers that use its feed warn visitors before the page loads. PhishDestroy lists the domain on its blocklist.
The page lived on a Netlify subdomain, which costs nothing and takes minutes to set up. That fits a throwaway operation that lasted about ten days after we first saw it. It was served from Amazon infrastructure in Germany. The DigiCert certificate is the platform's standard one, so the padlock said nothing about who ran the page.
If you entered a password on this page, change it on the real service and on any account that reuses it, then turn on two-factor authentication. If you typed a recovery phrase or private key, treat that wallet as compromised. Create a new wallet on a trusted device and move any remaining funds there right away. No legitimate service ever asks for a seed phrase through a website. Defenders should block the full hostname and look in proxy logs for users who reached it between 2026-09-05 and 2026-09-15.
Edge-IP itibarı bu etki alanıyla ilişkilendirilmez.
Location describes the IP network.
bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478netlify.appSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of trezou-iostre-us.netlify.app · checked Sep 15, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
trezou-iostre-us.netlify.app
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Bilinmiyor→inactive
http_no_content
Bilinmiyor→inactive
http_no_content
Bilinmiyor→inactive
http_no_content
Bilinmiyor→inactive
http_no_content
Bilinmiyor→inactive
http_no_content
Bilinmiyor→inactive
http_no_content
Bilinmiyor→inactive
http_no_content
Bilinmiyor→inactive
http_no_content
Bilinmiyor→inactive
http_no_content
Erişilebilir→Mevcut değil
No flag recorded→Flag recorded
Erişilebilir
Threat flag recorded
View source14/89 engine detections
View sourcetrezou-iostre-us.netlify.app
View source1 topluluk raporu
KategoriIMPERSONATION
Brand abuse: impersonation, fake affiliation, impersonating Trezor
Listed domains receive at least one abuse report; this entry has no retained notification history.
Hesap kimlik bilgilerini, kişisel bilgileri veya ödeme bilgilerini girdiyseniz ya da bu alan adından bir dosya indirdiyseniz hemen harekete geçin. Aşağıda olayı bildirmenize ve kendinizi korumanıza yardımcı olacak kaynaklar bulunmaktadır.
resmi siber suç iletişim bilgileri veya şikayet taslağı oluştur → almak için ülkenizi seçin.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
trezou-iostre-us.netlify.app)Tüm ayrıntıları bilmeseniz bile — yine de şikayette bulun. Kısmi bilgiler de soruşturmalara yardımcı olmaktadır.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Saklanan engelleme listesi, WHOIS, DNS ve genel tarama kanıtlarını kullanarak tehdit analizi
Şimdi TaraŞüpheli alan adlarını tehdit veritabanımıza bildirin — topluluğu koruyun
BildirSon kimlik avı raporları ve gözlemlenen kullanılabilirlik değişiklikleri
İzleCanlı tehditleri izleyin veya bunun yanlış bir uyarı olduğunu düşünüyorsanız bu kayda itiraz edin
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.