Skip to security report
royalsea.casino favicon
Domain security and threat intelligence

royalsea.casino

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

PhishDestroy first recorded royalsea.casino on 2026-09-08. Stored VirusTotal result: 15/92 engines flagged. Malicious: 13. Suspicious: 2. Analysis time (as stored): 2026-10-18 23:28 UTC. Retrieved (as stored): 2026-10-22 09:07 UTC.

Page title: “royalsea.casino | 522: Connection timed out”

More about the sources
Recorded security signals

Stored VirusTotal result: 15/92 engines flagged. Malicious: 13. Suspicious: 2. Analysis time (as stored): 2026-10-18 23:28 UTC. Retrieved (as stored): 2026-10-22 09:07 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 15/92
Registrar
NETIM SAS
Resolved IP
Canada172.67.165.28Cloudflare, Inc. · CDN
Registered
2025-06-26
First seen by PhishDestroy
2026-09-08
URLQuery
detections
Page captures
open gallery
Domain age
registered 2025-06-26 according to RDAP
2026-09-08 CDN

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded royalsea.casino on 2026-09-08. Stored VirusTotal result: 15/92 engines flagged. Malicious: 13. Suspicious: 2. Analysis time (as stored): 2026-10-18 23:28 UTC. Retrieved (as stored): 2026-10-22 09:07 UTC. Risk: critical (evidence score 100/100). Registrar: NETIM SAS. Status: Last known active. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
15 / 92
Scam type (automated label)
Gambling
Hosting
Canada172.67.165.28Cloudflare, Inc. · CDN
Registrar
NETIM SAS
Registered
2025-06-26
Page captures
4

PhishDestroy analysis, earlier unreviewed version

Overview

royalsea.casino presents itself as an online casino and is classified by PhishDestroy as a fraudulent gambling site. It targets people looking to play and deposit money online. PhishDestroy first flagged it on 2026-09-08. As of 2026-10-19 the domain was still alive and redirecting visitors elsewhere, so it remains a live risk.

How the scam works

Fraudulent casinos usually let new players register and deposit easily, often with bonuses or inflated early wins. The trouble starts at withdrawal. Payouts are delayed, blocked by sudden verification demands or extra fees, or the account is closed, and the deposits are gone. Players also hand over identity documents and payment details that can be reused against them. The page title at last capture was a Cloudflare "522: Connection timed out" error rather than casino content, while the domain itself kept responding with a redirect.

Evidence

On 2026-09-17, 17 of 89 VirusTotal engines flagged the domain. That is a meaningful share for a site that otherwise looks like an ordinary casino brand. The flagging vendors include BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, alphaMountain.ai, Bfore.Ai PreCrime, CyRadar and Chong Lua Dao. The domain also appears in 4 AlienVault OTX threat pulses, which means other researchers have tracked it independently. Among blocklists, it is currently listed by PhishDestroy.

Infrastructure

The domain was registered through NETIM SAS on 2025-06-26, more than fourteen months before PhishDestroy flagged it. That is a long-lived operation, not a throwaway domain. It sits behind Cloudflare, with the edge address located in Canada, so the real origin server is hidden from view. The Google Trust Services certificate is standard for Cloudflare-fronted sites and says nothing about legitimacy.

What to do

If you deposited money at royalsea.casino, stop sending funds and refuse any "fee" or "tax" demanded to unlock a withdrawal. Contact your bank or card issuer to dispute the charges, and save transaction records and chat logs. If you uploaded ID documents, watch for identity misuse. Change any password you reused on the site. Security teams should block the domain and its redirect targets at DNS and proxy level, and treat logged visits as possible financial exposure for the affected users.

Source evidenceVirusTotal 15 / 92 8 sources

VirusTotal

15 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 15 fields
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

Source
VirusTotal
Numerator
17
Denominator
89
Vendors
alphaMountain.ai, Bfore.Ai PreCrime, BitDefender, Chong Lua Dao, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, Lionic, Seclookup, SOCRadar, Sophos, VIPRE, Webroot
Checked at
2026-09-17 22:17:25

Gridinsoft

1/100

URLScan

Page capture

Open report
URLScanOriginal source recordObserved: 16 fields
Separate monitor record · 2026-09-19 03:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01a07fa1-e1bb-74cf-bafe-d8cda50aa067
Score
0
Malicious
✗
Result at
2026-09-19T03:30:19Z
Enriched at
2026-09-17T08:16:37Z
Source timestamps
Urlscan result at: 2026-09-19 05:30:19; Urlscan enriched at: 2026-09-17 10:16:37

PhishDestroy DOM

98 / 100 · heuristic score · 0 brand references · 1 classification

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 0 / 100 · 2026-09-17 02:20 UTC

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

Heuristic score
0
Analyzed at
2026-09-17T02:20:13Z
Source timestamp
2026-09-17 04:20:13
Technical metadata

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

AI title
royalsea.casino — Fraudulent Gambling Site
AI description
royalsea.casino is an online casino flagged as fraudulent, aimed at gamblers who risk losing deposits, winnings and the personal data they hand over at signup.
AI summary
Overview royalsea.casino presents itself as an online casino and is classified by PhishDestroy as a fraudulent gambling site. It targets people looking to play and deposit money online. PhishDestroy first flagged it on 2026-09-08. As of 2026-10-19 the domain was still alive and redirecting visitors elsewhere, so it remains a live risk. How the scam works Fraudulent casinos usually let new players register and deposit easily, often with bonuses or inflated early wins. The trouble starts at withdrawal. Payouts are delayed, blocked by sudden verification demands or extra fees, or the account is closed, and the deposits are gone. Players also hand over identity documents and payment details that can be reused against them. The page title at last capture was a Cloudflare "522: Connection timed out" error rather than casino content, while the domain itself kept responding with a redirect. Evidence On 2026-09-17, 17 of 89 VirusTotal engines flagged the domain. That is a meaningful share for a site that otherwise looks like an ordinary casino brand. The flagging vendors include BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, alphaMountain.ai, Bfore.Ai PreCrime, CyRadar and Chong Lua Dao. The domain also appears in 4 AlienVault OTX threat pulses, which means other researchers have tracked it independently. Among blocklists, it is currently listed by PhishDestroy. Infrastructure The domain was registered through NETIM SAS on 2025-06-26, more than fourteen months before PhishDestroy flagged it. That is a long-lived operation, not a throwaway domain. It sits behind Cloudflare, with the edge address located in Canada, so the real origin server is hidden from view. The Google Trust Services certificate is standard for Cloudflare-fronted sites and says nothing about legitimacy. What to do If you deposited money at royalsea.casino, stop sending funds and refuse any "fee" or "tax" demanded to unlock a withdrawal. Contact your bank or card issuer to dispute the charges, and save transaction records and chat logs. If you uploaded ID documents, watch for identity misuse. Change any password you reused on the site. Security teams should block the domain and its redirect targets at DNS and proxy level, and treat logged visits as possible financial exposure for the affected users. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a07fa1-e1bb-74cf-bafe-d8cda50aa067/ VirusTotal report: https://www.virustotal.com/gui/domain/royalsea.casino Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=royalsea.casino Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
AI generated by
threat-anthropic
AI generated at
2026-10-19T10:48:17Z
Revision
0d00cf094623e3ce97e281aa65a47b94ec7453d10ad26ebb3cb959eb3d6ff34e
Mode
stored
Interpretation
Earlier stored analysis, not reviewed; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 16 fields

Mail configuration

SPF lookups
0

CAA records

Domain
royalsea.casino

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
243

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

DNS servers

Nameservers
  • IP address
    173.245.59.139
    Host
    rick.ns.cloudflare.com
  • IP address
    108.162.194.220
    Host
    dalary.ns.cloudflare.com
DNS zone
royalsea.casino

Location

IP address
2606:4700:3035::ac43:a51c
ASN
13335
Organization
Cloudflare, Inc.
City
Toronto
Country
CA

TLS certificate

Issuer
Google Trust Services / WE1
Subject
royalsea.casino

DNS records

A
  • 172.67.165.28
  • 104.21.11.34
NS
  • dalary.ns.cloudflare.com
  • rick.ns.cloudflare.com
SOA
Primary nameserver
dalary.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2416914578
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2606:4700:3035::ac43:a51c
  • 2606:4700:3034::6815:b22

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
SAMEORIGIN
Referrer-Policy
same-origin
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2606:4700:3034::6815:b22
IP version
6

HTTP headers

Response headers
Server
cloudflare
Content-Type
text/html; charset=UTF-8
X-Frame-Options
SAMEORIGIN
Referrer-Policy
same-origin
Original source fields · JSON
Mail configuration
Spf lookups: 0
Caa records
Domain: royalsea.casino
Protective DNS results
Resolvers: 12; Blocked count: 0
Web archive observations
Last: 2025-07-10T00:14:49Z; First: 2025-07-10T00:14:49Z; Changes: 0; Days archived: 1; Avg page bytes: 243
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443, 8080
DNS server
NS: (IP: 173.245.59.139; Host: rick.ns.cloudflare.com), (IP: 108.162.194.220; Host: dalary.ns.cloudflare.com); Zone: royalsea.casino
Location
IP: 2606:4700:3035::ac43:a51c; ASN: 13335; Org: Cloudflare, Inc.; City: Toronto; Country: CA
SSL
Issuer: Google Trust Services / WE1; Subject: royalsea.casino
DNS records
A: 172.67.165.28, 104.21.11.34; NS: dalary.ns.cloudflare.com, rick.ns.cloudflare.com; Soa: Nsname: dalary.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2416914578; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2606:4700:3035::ac43:a51c, 2606:4700:3034::6815:b22
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: SAMEORIGIN; Referrerpolicy: same-origin; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Firewall
Waf: Cloudflare; Has waf: ✓
Get IP
IP: 2606:4700:3034::6815:b22; Family: 6
HTTP headers
Headers: Server: cloudflare; Content type: text/html; charset=UTF-8; X frame options: SAMEORIGIN; Referrer policy: same-origin
Security Signals
SA Scamadviser Warnings 21/100
The Tranco rank (how much traffic) is rather low Cryptocurrency services detected, these can be high risk We detected a possible gambling website Sport (betting) information was found on this site The website was reported in the last 30 days as threat by DNSFilter This site has been flagged as malicious by Bfore.ai
This website offers payment methods which offer a "money back services" We found a valid SSL certificate

Questions about royalsea.casino

Is royalsea.casino legit?

PhishDestroy rates royalsea.casino as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-09-08. Stored VirusTotal result: 15/92 engines flagged. Malicious: 13. Suspicious: 2. Analysis time (as stored): 2026-10-18 23:28 UTC. Retrieved (as stored): 2026-10-22 09:07 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is royalsea.casino safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on royalsea.casino. A confirmed blockchain transaction cannot be reversed.

What should I do if I used royalsea.casino?

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Downloaded a file — do not open it and scan the device with security software

Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (4)

All capture links and hashes (4)
Observed page title
royalsea.casino | 522: Connection timed out
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 30 days
royalsea.casino: caution — 17/89 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card royalsea.casino: caution — 17/89 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 366a23b96f15

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 92 report ↗
IP Context Canada172.67.165.28 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar NETIM SAS
Abuse contactabuse@netim.net
RegistrationCreated 2025-06-26 — Expires 2027-06-26
Registrant countryAustralia VirusTotal WHOIS
Registrant1f8f4166599d23ee0e9aa09a3888b250s@ VirusTotal WHOIS
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First Detected2026-09-08
DOM Analysisanalyzed 2026-09-17score 98/100
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

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.

Accreditation is a contract, not a safety certification.

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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada172.67.165.28
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 1

  • dalary.ns.cloudflare.com

SOA

  • nsname: dalary.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2416914578
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-09-23 19:03:46
Valid until
2026-12-22 20:02:19
Hostname match
Yes
Validity
Within stored validity dates
Collection time
2026-10-11 01:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprint9e0faecebc8894c1696c6fd4242991ce1543a64425d16141f8f9d137948ad046
Certificate names · 2 SANs
  • royalsea.casino
  • *.royalsea.casino

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-11-21 23:46 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting DNS: Resolved
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-11-21 23:46 UTC
RDAP registration
Observed timeline last reachable: 2026-11-21 23:46 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Casino / Gambling License Verification
Unverified gambling license
This domain markets casino/gambling services. Scam casinos routinely display fake Curaçao, MGA, or Kahnawake license badges that don’t exist in the real registries. Always verify the license number against the official regulator database before depositing. If the site shows a seal but no clickable registry link — or the linked registry page doesn’t exist — treat it as fraudulent.
Curaçao eGaming (official) Malta Gaming Authority UK Gambling Commission PA Gaming Control Kahnawake Gaming Gibraltar Gambling
Technologies · 2 identified
Open complete records

VirusTotal Analysis

15 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy Previous stored snapshot: 17 detections
ESET
VIPRE
G-Data
Lionic
Sophos
CyRadar
Webroot
Fortinet
SOCRadar
Kaspersky
Seclookup
Gridinsoft
BitDefender
alphaMountain.ai
Forcepoint ThreatSeeker
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data101
Open complete records

Captured network requests

Network requests: 8 SHA-256 hashes: 7 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 02:43 UTC.

Open this scan on URLScan 01a07fa1-e1bb-74cf-bafe-d8cda50aa067 ↗

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

Page titles differ

Our scanner could not complete this check.

Browser
royalsea.casino | 522: Connection timed out
Crawler
301 Moved Permanently
royalsea.casino
Saved result
Unreachable
Stored observation history24
Open complete records
Separate monitor HTTP observation

Source: domain_monitor. This stored snapshot does not establish current availability.

Observed · UTC
Recorded HTTP status
301
Probe value as recorded
301
Original source timestamp
2026-09-08 08:28:32
All retained availability observations235
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 8. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    royalsea.casino detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded recorded
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

3 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+438 d 16 h
  3. VirusTotal analysis with detections+40 d 17 h
  1. VirusTotal

    15/92 engine detections

    +31 d 15 h
  2. URLScan

    Page captured

    +9 d 2 h
  3. Added to PhishDestroy

    royalsea.casino

How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including royalsea.casino)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/royalsea.casino"
  title="PhishDestroy threat report for royalsea.casino"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>