Lompat ke laporan keamanan
Keamanan domain dan intelijen ancaman
lucky-bet898.casino favicon

lucky-bet898.casino

“LuckyBet Casino”

Registrar
NameCheap
Resolved IP
188.114.97.9
Registered
17/07/2026
PhishDestroy assessment Kritis
Ketersediaan Terakhir diketahui aktif Pengamatan keterjangkauan tersimpan terbaru Teramati · HTTP probe
Deteksi Total Virus: 4/91 Label merek otomatis: Google
OTX: 3 refs 14/09/2026 CDN
API
Domain ini telah ditandai sebagai berbahaya
Mesin keamanan melaporkan deteksi: 4. Berhati-hatilah — jangan memasukkan kredensial atau informasi pribadi.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Domain age
Ringkasan laporan

Penipuan judi: lucky-bet898.casino — Terakhir diketahui aktif (HTTP 200). Ringkasan bukti: VirusTotal 4/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker…

Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.

Source evidenceVirusTotal 4 / 91 · OTX 3 references 4 sources

VirusTotal

4 / 91 engine detections

Buka laporan

Google Safe Browsing

No threat flag

Buka laporan

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

Analysis

Kritis
VirusTotal
4 / 91
OTX
3 community refs

PhishDestroy threat report

Overview

lucky-bet898.casino presents itself as LuckyBet Casino, an online gambling site aimed at players looking for quick bets and bonuses. PhishDestroy classifies it as a fraudulent gambling operation and first flagged it on 2026-09-14. As of 2026-10-19 the site was still online and serving its casino content, so it remains a live risk to anyone who lands on it.

How the scam works

Sites like LuckyBet Casino usually attract players with generous sign-up bonuses or inflated early winnings, often accepting deposits in cryptocurrency. The balance shown on the dashboard grows, but withdrawals stall behind invented verification steps, turnover requirements or fees that must be paid up front. Victims lose whatever they deposit and any extra fees they pay, and personal or identity documents submitted for verification may also be kept.

Evidence

On 2026-09-27, 4 of 91 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker and SOCRadar. That is a modest count, but those vendors detected it independently of one another. The domain also appears in 3 AlienVault OTX threat pulses, which shows other researchers are tracking it. Among blocklists, it is currently listed by PhishDestroy.

Infrastructure

The domain was registered through NameCheap, Inc. on 2026-07-17, roughly two months before PhishDestroy detected it. A gap like that fits a site that builds traffic before it draws attention. It resolves to Cloudflare, Inc. addresses geolocated to Canada. Because Cloudflare acts as a reverse proxy, that location does not reveal where the actual server runs. The site's certificate is a standard automated one from Google Trust Services and says little about the operator.

What to do

Do not deposit anything more. In particular, do not pay any withdrawal, tax or unlock fee the site demands, because paying will not release your funds. If you paid by card or bank transfer, contact your bank right away about a chargeback, and save your transaction IDs, chat logs and screenshots for a report. If you uploaded identity documents, watch for identity misuse and change any password you reused on the site. Security teams should block the domain at the DNS and proxy level and add it to gambling and fraud filters.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Domain details

Domain
IP Context Cloudflare shared edge origin IP hidden Reputasi Edge-IP tidak dikaitkan dengan domain ini.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomaindrainerfraudmonthlyphishdestroyphishingscam
Registrar NameCheap US(US)
Kontak penyalahgunaan["abuse@namecheap.com"]
PendaftaranDibuat 17/07/2026 (95d) — Expires 17/07/2027
Status HTTP200
Detail teknisProvenance & timestamps
Pertama Kali Terdeteksi14/09/2026
Favicon Hash
ICANN OVERSIGHT

Akreditasi dan konteks RAA

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 Tidak ada yang dikirim secara otomatis.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.9
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Reputasi Edge-IP tidak dikaitkan dengan domain ini.

Server nama 1

  • moura.ns.cloudflare.com

Location describes the IP network.

Sertifikat TLS

Issuer
Google Trust Services / WE1
Valid from
2026-09-27 23:06:44
Valid until
2026-12-27 00:05:31
Validity
Within stored validity dates
Collection time
2026-10-11 04:02:53 UTC
Collection source
PhishDestroy collector
Certificate fingerprintfc3bdb794ac7b3c62d9e7a7e5e6b37b9023a3f8f5a07aa4e306b7941e3d5cdf4

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-10-20 10:07:17 UTC

Primary outcome Konten aktif reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Konten aktif Ordinary HTTP content served 90% 2026-10-20 10:07:17 UTC
RDAP registration Tidak diketahui
Observed timeline last reachable: 2026-10-20 10:07:17 UTC last content: 2026-10-20 10:07:17 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
Teknologi · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Laporkan Domain Ini Kirimkan bukti & bantu lindungi orang lain

Analisis VirusTotal

4 / Vendor keamanan 91 menandai domain ini
View on VT
Last analyzed First positive detection Previous stored snapshot: 4 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
SOCRadar
Analisis Performa Situs

Google PageSpeed Insights — mobile performance audit of lucky-bet898.casino · checked Sep 21, 2026

70
Needs Work
Performance
FCP
2.65s
First Contentful Paint
LCP
6.53s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
37ms
Total Blocking Time
SI
4.66s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

Last reachable observation
Last content 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.

Stored observation history22

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  2. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  3. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  4. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  5. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

Earlier observations 17
  1. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  2. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  3. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  4. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  5. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  6. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  7. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  8. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  9. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  10. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  11. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  12. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  13. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  14. VirusTotal · Detection count

    2→3

  15. VirusTotal · Detection count

    1→2

  16. VirusTotal · Detection count

    0→1

  17. Availability monitor · First collection record

    Dapat dijangkau

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    4/91 engine detections

    View source
  3. AlienVault OTX

    3 community references

    View source
  4. Added to PhishDestroy

    lucky-bet898.casino

    View source

Intelijen komunitas

1 laporan komunitas

KategoriOTHER

A scammer contacted me offering to play on a fake casino website (https://lucky-bet898.casino). After playing for 3 days, the system displayed fake winnings. When I requested a withdrawal, the platform demanded an upfront deposit / verification fee of 95 USDT and 160 USDT to TRC-

Check for cloaking

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

lucky-bet898.casino

Bukti & Laporan Eksternal

Community Scam Report — ChainAbuse
1 report filed for lucky-bet898.casino (1 written by a person) · category: Other · source checked
“A scammer contacted me offering to play on a fake casino website (https://lucky-bet898.casino). After playing for 3 days, the system displayed fake winnings. When I requested a withdrawal, the platform demanded an upfront deposit / verification fee of 95 USDT and 160 USDT to TRC-20 addresses: TAAdxSb8gJreUrGahLJHcuiyD3ZV1QKMCo and TVJWgjUPkgDHLVRLJmnZdejtrDFCKverq5. This is an advance-fee fraud scheme attempting to steal crypto funds.”
— reported by Anonymous on Sep 14, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
Analisis Mendalam
Help & reporting

Apakah Anda Terpengaruh oleh Situs Ini?

2 evidence signal groups linked 0 stored notification records Terakhir diketahui aktif

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.

Official reporting routes

Waspadalah terhadap penipu yang mengatasnamakan pemulihan! Penjahat dapat menghubungi korban lagi sambil berpura-pura menjadi penyelidik, pengacara, atau agen pemulihan. Jangan membayar biaya di muka atau membagikan kredensial. Pelajari lebih lanjut tentang penipuan dalam proses pemulihan →

Laporkan kepada Pihak Berwenang di Daerah Anda

Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.

Direktori 97 negara

Template-based draft · optional AI wording assistance requires separate consent

Draf yang dibantu AI — detail insiden diproses oleh penyedia AI · Tinjau dan kirimkan sendiri
After a phishing incident

Rekomendasi & Saran bagi Para Korban

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

Apa yang harus saya lakukan segera?

Mendesak

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

  • Ubah semua kata sandi — email, akun Exchange, apa pun yang menggunakan kata sandi yang sama
  • Aktifkan 2FA menggunakan aplikasi otentikator (bukan SMS). Nonaktifkan pemulihan berbasis SMS
  • Kartu pembeku jika Anda telah memasukkan detail perbankan di situs phishing tersebut

Informasi apa saja yang sebaiknya saya kumpulkan untuk laporan saya?

Pedoman FBI

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.
  • Tanggal dan waktu yang tepat — dari setiap transaksi dan kontak pertama dengan penipu
  • Tangkapan layar — situs web penipuan, pesan obrolan, email, transaksi dompet digital, media sosial
  • Semua URL & domain digunakan oleh penipu (termasuk lucky-bet898.casino)
  • Komunikasi — email, pesan teks, nomor telepon, dan nama pengguna yang digunakan oleh penipu tersebut

Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.

Ke mana saya harus melaporkan penipuan ini?

  • FBI IC3 — Pusat Pengaduan Kejahatan Internet (Laporan tingkat federal AS)
  • Europol — Pelaporan kejahatan siber di Eropa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Polisi setempat — membuat catatan resmi, meskipun mereka tidak dapat bertindak segera

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?

  • Situs web palsu — salinan yang persis sama dengan situs asli, dengan domain yang sedikit diubah
  • Pemotongan babi — kepercayaan yang dibangun selama beberapa minggu melalui Telegram/WhatsApp/aplikasi kencan, lalu uangnya dicuri
  • Penipuan pemulihan — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Penipuan yang didukung oleh kecerdasan buatan — deepfakes, serangan phishing otomatis, dan situs yang dihasilkan oleh kecerdasan buatan (AI) yang membuat penipuan semakin sulit dideteksi

Bagaimana cara saya melindungi diri di masa depan?

  • Tandai situs resmi — jangan pernah mengklik tautan dari email, pesan langsung (DM), atau iklan
  • Memverifikasi domain — periksa PhishDestroy Sebelum berinteraksi. Periksa HTTPS, ejaan, dan usia domain
  • "Terlalu bagus untuk jadi kenyataan" = penipuan — imbal hasil yang dijamin, dukungan dari selebriti, tenggat waktu yang mendesak

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

Tetap Terinformasi, Tetap Aman

Pantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive

Pemberitahuan Ancaman Real-Time Ajukan Banding Terhadap Iklan Ini
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

Sematkan Laporan Ini

Bagikan informasi ancaman ini di situs web atau blog Anda

embed.html
<iframe
  src="https://phishdestroy.io/id/embed/domain/lucky-bet898.casino"
  title="PhishDestroy threat report for lucky-bet898.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>