Why this matters — ICANN RAA §3.18 obligation & victim-assistance
On PhishDestroy delivered an evidence-backed abuse report
(repeated 3 times, most recently ) to abuse@namecheap.com with the evidence stored for the case at that time.
More than 5 months later, the phishing infrastructure remains reachable
.
Under ICANN RAA §3.18 accredited registrars are contractually obliged to “take reasonable and prompt steps to investigate and respond appropriately to any reports of abuse.” Silence beyond 24 hours after a documented notification with verifiable evidence is not a timing issue — it is a policy decision to let the operation continue. PhishDestroy\'s position: where a registrar fails to act on clear evidence, the registrar has aligned itself with the operator of the scheme and bears co-responsibility for downstream harm caused to victims from the moment of notification onward.
Victim-assistance obligation. If NameCheap, Inc. doesn't consider the listed detections enough proof — that is interesting in itself, given the volume of independent vendor confirmations. But after 3 separate notifications over 5 months, with the operation still active, the registrar took no measurable action to mitigate the harm caused by their client. The reasonable next step is direct help to any identified victims — contact & payment-trail disclosure, abuse-thread transcripts, registrant data preservation — since the registrar chose, by inaction, to extend the window of damage.
royalx[.]cc
Phishing- und Sicherheitsprüfung für royalx.cc
“Royal X Casino Game Download 2026 Apk Latest Version V2.48.9”
royalx.cc — Letzter bekanntermaßen aktiv (HTTP 200). Betrugstyp: Gambling. Zusammenfassung der Beweislage: VT 8/91 (ADMINUSLabs, alphaMountain.ai, BitDefender, CyRadar, ESET); URLQuery 2 alerts; URLScan no malicious verdict; GSB no flag; BL 0; PD 89/100. Registrar: NameCheap.
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
royalx.cc entered the PhishDestroy evidence set on Feb 26, 2026. The stored content classification is gambling. The assembled evidence scores 89/100 (high).
Two independent sources are positive: VirusTotal and URLQuery. VirusTotal recorded 8 detections among 91 engines: ADMINUSLabs, alphaMountain.ai, BitDefender, CyRadar, ESET, Forcepoint ThreatSeeker, G-Data, Gridinsoft on Jul 27, 2026 at 02:21 UTC. URLQuery recorded 2 threat-system alerts on Apr 28, 2026 at 21:59 UTC. The evidence is not unanimous. The external blocklist snapshot contained no matches on Aug 7, 2026 at 14:20 UTC. Google Safe Browsing returned no flag on Mar 2, 2026 at 20:57 UTC. URLScan completed without a malicious verdict (score 0) on Mar 27, 2026 at 12:47 UTC.
HTTP 200 was recorded on Aug 7, 2026 at 10:24 UTC. Registration records for the domain list NameCheap, Inc. as the registrar and Feb 21, 2026 as the creation date. Registration preceded first observation by 5 days. At collection time, the hostname resolved to 63.250.38.156 on AS22612 (NAMECHEAP-NET, US). The associated network metadata labels the endpoint as AS22612 Namecheap, Inc. in Phoenix, US. The stored server header is LiteSpeed. Captured page title: “Royal X Casino Game Download 2026 Apk Latest Version V2.48.9”. DOM analysis completed on Jul 9, 2026 at 02:22 UTC; stored DOM score 78/100. The evidence archive retains 4 visual captures from PhishDestroy, URLScan, and URLQuery. IoC extraction completed on Jul 29, 2026 at 02:30 UTC; stored 0 format-validated wallet addresses and 0 Telegram indicators. TLS metadata lists Sectigo Public Server Authentication CA DV R36 as the certificate issuer.
No target brand has been confirmed from stored page content; hostname wording alone is not treated as brand evidence. Taken together, the page content and independent findings support classifying this hostname as gambling.
Erkenntnisse zur Netzwerksicherheit
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Hagezi Threat Feed | royalx.cc |
malicious | Sinkholed |
| DNS4EU | royalx.cc |
malicious | Sinkholed |
Pipeline zur Reaktion auf Sicherheitsbedrohungen
Status der öffentlichen Sperrliste
Verlauf der Missbrauchsmeldungen · 3 stored reports over 86 days · click to expand
-
Report #1 Feb 8, 2026 · 18:34 UTCPhishing Abuse Report: royalx[.]ccsupport@namecheap.com
-
Report #2 ICANN CC 1899h still active Apr 29, 2026 · 00:57 UTCESCALATION #2 (1899h active): Phishing - royalx[.]ccabuse@namecheap.com abuse@verisign-grs.com compliance@icann.org
-
Report #3 ICANN CC 2048h still active May 5, 2026 · 06:03 UTCESCALATION #3 (2048h active): Phishing - royalx[.]ccabuse@namecheap.com abuse@verisign-grs.com compliance@icann.org
Casino / Gambling License Verification
Technologien · 1 identified
High-performance web server compatible with Apache configurations.
VirusTotal-Analyse
Website-Performanceanalyse
Google PageSpeed Insights — mobile performance audit of royalx.cc · checked Mar 2, 2026
Nachweise und externe Berichte
Wurden Sie von dieser Website betroffen?
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.
Melden Sie sich bei Ihren örtlichen Behörden
Wählen Sie Ihr Land aus, um Offizielle Kontakte im Bereich Cyberkriminalität oder einen Beschwerdeentwurf erstellen → zu erhalten.
Jede beliebige Domain prüfen
Bedrohungsanalyse anhand gespeicherter Blocklisten, WHOIS, DNS und öffentlicher Scan-Beweise
Jetzt scannenPhishing melden
Melden Sie verdächtige Domains an unsere Bedrohungsdatenbank – schützen Sie die Community
MeldenEchtzeit-Bedrohungsfeed
Aktuelle Phishing-Meldungen und beobachtete Verfügbarkeitsänderungen
ÜberwachenBleiben Sie auf dem Laufenden, bleiben Sie sicher
Beobachten Sie aktuelle Bedrohungen oder legen Sie Widerspruch gegen diesen Eintrag ein, wenn Sie der Meinung sind, dass es sich um einen Fehlalarm handelt