VirusTotal
7 / 91
“Tron - TRC20 | Secure Payment Gateway”
trc20tron.exchange — Letzter bekanntermaßen aktiv (HTTP 200). Markenidentität: Genericcrypto; Betrugstyp: Fake Exchange. Zusammenfassung der Beweislage: VirusTotal 7/91 (alphaMountain.ai, BitDefender, Forcepoint ThreatSeeker, Fortinet, G-Data); URLScan malicious verdict; Spamhaus DBL_PHISH; PhishDestroy score 100/100. Registrar: NameCheap.
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
7 / 91
malicious
Melden4/14
DBL_PHISH
checked — no match recorded
24 community references
Meldenprovider verdict: suspicious
Meldengespeicherter Bericht
Melden Checked; no threat flag recorded
MeldenThe domain trc20tron.exchange, associated with a generic phishing operation, has a critical threat score of 95/100 and is currently down. Sixteen out of 95 security vendors have flagged this domain as malicious, including notable names like BitDefender and Google Safe Browsing, and it is listed on one public blocklist.
Registered with NameCheap, Inc., the domain was created on February 21, 2026, and was first seen on February 19, 2026. The hosting IP is 13.52.188.95. The down status indicates that it has likely been taken down due to its malicious activities.
Immediate action is required: block the domain at the perimeter and submit a report to the registrar's abuse desk.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
TLkEv64jk1bwYaEL8fVdiaeSFQkHE8UcYmFormat validated · Domain analysisTXR54s2n8QvyX8du94jiorYE681NCqoqeYFormat validated · Domain analysisIoC extraction recorded 2026-07-29 02:32:59 UTC
Gespeicherte Beobachtungen zum Vergleich zwischen Crawler und Browser für diesen Host sowie eine Echtzeit-Fingerabdruckprüfung für Verkehrsverteilungssysteme im Keitaro-Stil.
NetlifyAnmerkung des Scanners: alive_content: raw=ok; http=200; via=https_proxy; server=Netlify
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.
Die Edge-IP-Reputation wird dieser Domäne nicht zugeordnet.
dns2.registrar-servers.comeforward1.registrar-servers.compriority 10eforward3.registrar-servers.compriority 10eforward2.registrar-servers.compriority 10eforward4.registrar-servers.compriority 15eforward5.registrar-servers.compriority 20Location describes the IP network.
62240783d205f333d96968729102c8e1df8bf3dd239ab4fabbdb9776365ea01bwww.trc20tron.exchangeSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Von 1 Community-Mitglied gemeldet; erstmals gesehen am 19.02.2026
Wenn Sie Kontoanmeldeinformationen, persönliche oder Zahlungsinformationen eingegeben oder eine Datei von dieser Domain heruntergeladen haben, ergreifen Sie sofort Maßnahmen. Nachfolgend finden Sie Ressourcen, die Ihnen helfen, den Vorfall zu melden und sich zu schützen.
Wählen Sie Ihr Land aus, um Offizielle Kontakte im Bereich Cyberkriminalität oder einen Beschwerdeentwurf erstellen → zu erhalten.
Template-based draft · optional AI wording assistance requires separate consent
Bedrohungsanalyse anhand gespeicherter Blocklisten, WHOIS, DNS und öffentlicher Scan-Beweise
Jetzt scannenMelden Sie verdächtige Domains an unsere Bedrohungsdatenbank – schützen Sie die Community
MeldenAktuelle Phishing-Meldungen und beobachtete Verfügbarkeitsänderungen
ÜberwachenBeobachten Sie aktuelle Bedrohungen oder legen Sie Widerspruch gegen diesen Eintrag ein, wenn Sie der Meinung sind, dass es sich um einen Fehlalarm handelt