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). 브랜드 사칭: Genericcrypto; 사기 유형: Gambling. 증거 요약: VirusTotal 9/89 (alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet); URLScan malicious verdict; Spamhaus DBL_PHISH; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100. 등록기관: Fewmoretaps OU d/b/a T….
원본 포렌식 기록을 보존하기 위해 아래의 상세 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.
AI-assisted evidence review
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.
urlscan.io scan and screenshot: https://urlscan.io/result/01a06f30-5fdb-7155-a2e0-15201cce01f9/
VirusTotal report: https://www.virustotal.com/gui/domain/royalcore.net
Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=royalcore.net
Archived copy: https://web.archive.org/web/20260921204243/https://royalcore.net/
Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/
Site owner? Request a review: https://phishdestroy.io/appeals/
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
접속 가능
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.