VirusTotal
9 / 89 engine detections
打开报告“Royalcore: Most Popular Online Crypto Casino Based on Blockchain”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@trustname.com.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
加密赌场诈骗: royalcore.net — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 9/89 (alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet); URLScan…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
9 / 89 engine detections
打开报告DBL_PHISH
恶意
打开报告4 community references
打开报告provider verdict: clean
打开报告80/100
打开报告No threat flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
royalcore.net presents itself as "Royalcore: Most Popular Online Crypto Casino Based on Blockchain". PhishDestroy classifies it as a fraudulent gambling site aimed at cryptocurrency users looking for a blockchain casino. We first detected it on 2026-09-05. As of 2026-10-19 the site was still online and serving its casino content.
The site runs on the Gambler Scam kit, a template for fake casinos that look legitimate and show a balance that seems to grow. Victims deposit crypto to play and may see winnings pile up. When they try to cash out, the withdrawal stalls, gets rejected, or is held back until they pay another "fee", "tax" or "verification deposit". The money sent in is lost, and every extra payment made to unlock the balance only adds to the loss.
On 2026-09-13, 9 of 89 VirusTotal engines flagged the domain. Among them were Kaspersky, BitDefender, Fortinet, Forcepoint ThreatSeeker, G-Data, alphaMountain.ai, CRDF and SOCRadar, a spread of major vendors that goes well beyond a single outlier. urlscan.io rated the site malicious and matched it to generic crypto and crypto-scam brand patterns. Spamhaus lists it in its DBL as phishing. MetaMask and SEAL block it alongside PhishDestroy, and it appears in 4 AlienVault OTX threat pulses.
The domain was registered on 2026-05-21 through Fewmoretaps OU d/b/a Trustname.com, about three and a half months before we detected it. That gap leaves room for the site to build up some apparent history before going after players. It sits behind Cloudflare, so the visible address belongs to Cloudflare's network, geolocated to Canada, and not to the operator's own server.
Do not deposit anything on royalcore.net. If you already have, do not pay any withdrawal, tax or unlock fee, because those payments are part of the scam. Gather your transaction hashes, deposit addresses and any screenshots. Then report the case to the exchange you sent funds from and to your local cybercrime authority. If you signed up with a password you use elsewhere, change it on those accounts. Defenders should block the domain at DNS and web proxies and add it to crypto-wallet and browser warning lists.
Last checked
Edge-IP 声誉不属于此域。
moura.ns.cloudflare.comophelia.ns.cloudflare.comLocation describes the IP network.
86603e8c1d6bf67511e0772eab17ebf300a3177884ecf93ac2b11e1a99f3bd4fSaved 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 royalcore.net · checked Sep 5, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
可访问
4 community references
View sourceNo threat flag
View source9/89 engine detections
View source⚠️ ESCALATION #1 (0h active): Phishing - royalcore[.]net
royalcore.net
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
royalcore.net
PD-1788736028-royalcore.net Recipient: abuse@trustname.com 如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
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 ↗
royalcore.net)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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
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.