VirusTotal
6 / 89 engine detections
보고서 열기
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@gen.xyz.
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.
royalbet-oyunlar.icu — 연결 가능 · 액세스가 제한됨 (HTTP 403). 사기 유형: Impersonation. 증거 요약: VirusTotal 6/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, LevelBlue); PhishDestroy score 88/100. 등록기관: Fewmoretaps OU d/b/a T….
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
6 / 89 engine detections
보고서 열기checked — no detections recorded
보고서 열기4 community references
보고서 열기provider verdict: clean
보고서 열기No threat flag
보고서 열기No malicious flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
AI-assisted evidence review
royalbet-oyunlar.icu is an impersonation phishing site. Its name pairs the Royalbet betting brand with the Turkish word for "games," which points it at Turkish-speaking gamblers looking for that platform. PhishDestroy first flagged it on 2026-09-05. As of 2026-10-19 the site was still online, with its content behind a protection layer.
Lookalike betting domains copy a known brand so that players log in, register or deposit on a site the real operator does not control. Anything typed there, including usernames, passwords, card numbers, identity documents and deposit payments, goes to the operators. Victims typically lose their account access and any money they send. The page title reads "Just a moment...", which is a browser-check screen and not branded betting content, while our classification is impersonation phishing.
Six of 89 VirusTotal engines flagged the domain in a scan on 2026-09-18: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, LevelBlue and SOCRadar. That count is modest, but it comes from six unrelated vendors, so the verdict does not rest on one source. The domain also appears in four AlienVault OTX threat pulses, which means other researchers have tracked it independently. Among public blocklists, PhishDestroy currently lists it.
The domain was registered on 2026-06-17 through Fewmoretaps OU d/b/a Trustname.com, about eleven weeks before it was detected. Traffic passes through Cloudflare, Inc. on an address geolocated to Canada, so the real origin server is hidden from view. The cheap .icu extension and a disposable brand-plus-keyword name are typical of throwaway gambling clones that are replaced as soon as they are blocked.
If you logged in here, change your Royalbet password right away, and change it anywhere else you used the same one. Turn on two-factor authentication through the official app or website. If you entered card details or made a deposit, contact your bank or card issuer to dispute the charge and request a new card. If you uploaded ID documents, watch for identity misuse. Defenders should block the domain at DNS and proxy level and add it to filters for gambling-themed phishing aimed at Turkish users.
urlscan.io scan and screenshot: https://urlscan.io/result/01a06f2d-f8b0-765e-8f23-5bfe78ae3503/
VirusTotal report: https://www.virustotal.com/gui/domain/royalbet-oyunlar.icu
Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=royalbet-oyunlar.icu
Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/
Site owner? Request a review: https://phishdestroy.io/appeals/
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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.
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
alina.ns.cloudflare.comhal.ns.cloudflare.comLocation describes the IP network.
eeb0f47360d0a497edeebe703ca33c94c953c9832f0f325bbffef8aa7e6bc44aSaved 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 royalbet-oyunlar.icu · 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.
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
5→6
접속 가능
4 community references
View sourceNo threat flag
View source6/89 engine detections
View sourcePD-20260905-9AA606
royalbet-oyunlar.icu
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
royalbet-oyunlar.icu
PD-20260905-9AA606 Recipient: abuse@gen.xyz 계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
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 ↗
royalbet-oyunlar.icu)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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.