VirusTotal
13 / 93 engine detections
Buka laporan“Roy: Most Popular Online Crypto Casino Based on Blockchain”
Penipuan kasino kripto: roy.casino — Konten tidak tersedia. Ringkasan bukti: VirusTotal 13/93 (alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET); URLQuery…
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
13 / 93 engine detections
Buka laporan100 det.
1/100
Buka laporanBerbahaya
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 the domain roy.casino, registered on October 09, 2025 through NameCheap, Inc., indicates that it was used to host a fraudulent cryptocurrency casino page titled “Roy: Most Popular Online Crypto Casino Based on Blockchain”. The site resolved to the IP address 188.114.96.3, which belongs to AS13335 Cloudflare, Inc. in the United States. Cloudflare’s authoritative name servers clyde.ns.cloudflare.com and ursula.ns.cloudflare.com were configured for the domain. No TLS certificate was observed, and the site was taken offline at the time of reporting (July 23, 2026).
The page was built with the publicly available “Gambler Scam” phishing kit, a toolkit commonly employed to mimic gambling or casino services in order to lure victims into depositing cryptocurrency. Threat‑intelligence aggregators have assigned a Gridinsoft trust score of 1 out of 100, reflecting extreme suspicion. VirusTotal scans recorded 13 detections out of 93 security vendors, confirming that multiple antivirus engines flag the domain as malicious. The domain appears on one external security blocklist and has been listed by PhishDestroy, further evidencing its use in phishing campaigns.
The primary uncertainty concerns the current activity of the underlying infrastructure; because the site is offline, it is unclear whether the operators have relocated to a different host or continue to use the same IP range. Defensive recommendations include adding 188.114.96.3 to network block lists, enforcing DNS filtering for the domain and its Cloudflare name servers, and monitoring for any re‑registration attempts. Organizations should also educate users about crypto‑casino scams and advise them to verify domain ownership before any financial transaction. Continuous monitoring of VirusTotal, threat‑intel feeds, and new registrations similar to roy.casino is advised to detect potential resurgence.
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.
Reputasi Edge-IP tidak dikaitkan dengan domain ini.
clyde.ns.cloudflare.comursula.ns.cloudflare.comLocation describes the IP network.
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='roy.casino', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SOC
roy.casino
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
https://radar.cloudflare.com/scan/4bc9c579-c45c-4d85-9a22-27fdd238187c
13/93 engine detections
View sourceNo threat flag
View sourcePage captured
View sourceroy.casino
View sourceDilaporkan oleh 1 anggota komunitas; pertama terlihat 25/12/2025
Listed domains receive at least one abuse report; this entry has no retained notification history.
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 ↗
roy.casino)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.