VirusTotal
5 / 91 engine detections
Buka laporan“Royal Trader | CFD Trading — Trading on Stocks, Gold, Oil, Indices”
Phishing kripto: royaltradertrust.online — Konten tidak tersedia. Ringkasan bukti: VirusTotal 5/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker…
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
5 / 91 engine detections
Buka laporan2 det.
Buka laporan3/14
Berbahaya
Buka laporanno community references
Buka laporanprovider verdict: clean
Buka laporanNo threat flag
Buka laporanResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
Analysis of royaltradertrust.online shows a newly registered domain (created 27 Jan 2026) hosted on IP 163.61.188.7, which resolves to a United States location associated with MIT. The domain is served over HTTPS with a Let’s Encrypt certificate and returns HTTP 200. Technical fingerprints include LiteSpeed web server, Tailwind CSS, Alpine.js, jQuery (via CDN), Unpkg, Smartsupp, and embedded YouTube content. Gridinsoft assigns a trust score of 0/100, and VirusTotal reports four of ninety‑one AV engines flagging the site. The domain appears on one security blocklist and is listed as blocked by PhishDestroy. It is classified as a generic phishing threat with a high risk rating and remains active. Defenders should add the domain and its IP address to firewall deny lists, configure DNS filtering to block resolution, and monitor for any related C2 activity. Because only the page title “Royal Trader | CFD Trading — Trading on Stocks, Gold, Oil, Indices” is known, further content analysis is required to confirm credential‑stealing mechanisms. Continuous threat‑intel feeds should be consulted for updates, and any observed traffic to the domain should be investigated for possible compromised credentials.
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.
dns1.lytehosting.comdns2.lytehosting.comdns3.lytehosting.comdns4.lytehosting.comLocation describes the IP network.
680d2ed6a4d758989186197cf7eb0dfabe50bbd9758244a1e13877a38b86c6cdSaved 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 royaltradertrust.online · checked Jul 1, 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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='royaltradertrust.online', port=80): Max retries exceeded with url: / (Caused by NewConnect
royaltradertrust.online
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Tidak tersedia→Dapat dijangkau
Dapat dijangkau→Tidak tersedia
4→4
5/91 engine detections
View sourcePD-20260701-EA3FEA
No threat flag
View sourceroyaltradertrust.online
View sourcePage captured
View source1 laporan komunitas
KategoriOTHER_INVESTMENT_SCAM
Data submited by Intelligence for good
PD-20260701-EA3FEA Recipient: abuse@whiteprivacy.com 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.
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
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 ↗
royaltradertrust.online)Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.
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
Analisis ancaman menggunakan daftar blokir yang disimpan, WHOIS, DNS, dan bukti pemindaian publik
Pindai SekarangLaporkan domain yang mencurigakan ke basis data ancaman kami — lindungi komunitas
LaporanLaporan phishing terbaru dan perubahan ketersediaan yang diamati
PantauPantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive
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.