VirusTotal
17 / 93 engine detections
Raporu aç“TRON AIRDROP”
Sahte airdrop: telegram.financial — İçerik kullanılamıyor. Kanıt özeti: VirusTotal 17/93 (ADMINUSLabs, alphaMountain.ai, BitDefender, CRDF, CyRadar); URLQuery…
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
17 / 93 engine detections
Raporu aç4 threat-system alerts
Raporu açchecked — no match recorded
14 community references
Raporu açprovider verdict: clean
Raporu açNo threat flag
Raporu açNo malicious flag
Raporu açResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Cloudflare DNS | telegram.financial |
malicious | Sinkholed |
| DNS4EU | telegram.financial |
malicious | Sinkholed |
| Cloudflare DNS | service.telegram.financial |
malicious | Sinkholed |
| DNS4EU | service.telegram.financial |
malicious | Sinkholed |
PhishDestroy threat report
This domain, telegram.financial, is identified as a brand impersonation threat targeting TRON users through a fraudulent airdrop scheme. The site presents itself as an official TRON promotion, leveraging the Telegram branding in its domain name to deceive users into believing it is a legitimate distribution of tokens. Analysis of the page title, 'TRON AIRDROP,' confirms the intent to exploit trust in the TRON ecosystem, likely aiming to harvest wallet credentials or distribute malicious payloads under the guise of a token giveaway.
Technical evidence supports the classification of this domain as malicious. The domain was registered on February 21, 2026, through HOSTINGER operations, UAB, and currently resolves to the IP address 104.21.20.197, hosted on Cloudflare infrastructure (AS13335). Security vendors on VirusTotal flagged the domain with 17 out of 95 detections, indicating a consensus on its malicious nature. Additionally, the domain appears on one security blocklist, and no SSL certificate is present, further reducing its legitimacy. The absence of encryption and the use of a recently created domain align with common phishing tactics.
Users who visited telegram.financial should take immediate action to mitigate potential risks. If any credentials, wallet addresses, or personal information were entered, users must revoke access to any associated wallets or accounts and monitor for unauthorized transactions. It is recommended to scan the device used to access the site for malware, as phishing pages often deploy additional payloads. Users should also report the domain to their security providers and consider updating passwords or recovery phrases for any cryptocurrency wallets that may have been exposed. Vigilance against similar scams is advised, particularly those leveraging high-profile blockchain projects or social media branding.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Edge-IP itibarı bu etki alanıyla ilişkilendirilmez.
amber.ns.cloudflare.comrommy.ns.cloudflare.comLocation describes the IP network.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='telegram.financial', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
telegram.financial
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
https://radar.cloudflare.com/scan/542ba719-058f-444a-8947-fcf7eb84ed14
No threat flag
View source14 community references
View source17/93 engine detections
View sourcePD-20260125-2A5C13
telegram.financial
View sourcePage captured
View source1 topluluk üyesi tarafından bildirildi; ilk görülme 24.01.2026
PD-20260125-2A5C13 Recipient: abuse@hostinger.com Registrar: Hostinger Operations UAB (Lithuania (EU)) Policy Violations: AUP prohibits illegal activity including fraud, phishing, malware hosting; Hostinger may suspend/terminate services and domains Applicable Laws: Lithuanian Criminal Code (Ch. XXX, §§196–198 data/system crimes; §§214–215 electronic fraud); EU Directive 2013/40/EU
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 ↗
telegram.financial)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.