Lompat ke laporan keamanan
⚠️
Domain ini telah ditandai sebagai berbahaya
Mesin keamanan melaporkan deteksi: 13. Berhati-hatilah — jangan memasukkan kredensial atau informasi pribadi.
REGISTRAR NEGLIGENCE · EGREGIOUS PDR Ltd. d/b/a PublicDomainRegistry.com was notified 6 months ago — the threat is still operational.
Why this matters — ICANN RAA §3.18 obligation & victim-assistance

On PhishDestroy delivered an evidence-backed abuse report (repeated 14 times, most recently ) to abuse-contact@publicdomainregistry.com with the evidence stored for the case at that time. More than 6 months later, the phishing infrastructure remains reachable .

Under ICANN RAA §3.18 accredited registrars are contractually obliged to “take reasonable and prompt steps to investigate and respond appropriately to any reports of abuse.” Silence beyond 24 hours after a documented notification with verifiable evidence is not a timing issue — it is a policy decision to let the operation continue. PhishDestroy\'s position: where a registrar fails to act on clear evidence, the registrar has aligned itself with the operator of the scheme and bears co-responsibility for downstream harm caused to victims from the moment of notification onward.

Victim-assistance obligation. If PDR Ltd. d/b/a PublicDomainRegistry.com doesn't consider the listed detections enough proof — that is interesting in itself, given the volume of independent vendor confirmations. But after 14 separate notifications over 6 months, with the operation still active, the registrar took no measurable action to mitigate the harm caused by their client. The reasonable next step is direct help to any identified victims — contact & payment-trail disclosure, abuse-thread transcripts, registrant data preservation — since the registrar chose, by inaction, to extend the window of damage.

Elapsed since first report
6 months
Reports sent
14
Latest case ID
PD-1770100221-luhkas.com
Current status
Serving traffic (alive)
Keamanan domain dan intelijen ancaman

luhkas[.]com

Pemeriksaan phishing dan keamanan luhkas.com

“Luhkas: Most Popular Online Crypto Casino Based on Blockchain”

Putusan ancaman Kritis 100/100 skor bukti
Ketersediaan Terakhir diketahui aktif Pengamatan keterjangkauan tersimpan terbaru
Sinyal risiko
Deteksi Total Virus: 13/91 URLQuery threat systems: 3 alerts Peniruan identitas merek: Genericcrypto Terakhir diketahui aktif
13/91 VT URLQuery: 3 threat alerts 13/10/2025 Genericcrypto Penipuan Terkait Perjudian Crypto Scam 14 Reports Sent CDN
Ringkasan laporan

luhkas.com: 13 dari 91 pemindai VirusTotal menandai domain ini. Tinjau DNS, SSL, registrar, daftar blokir, dan data ancaman.

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

Ringkasan bukti
KRITIS
Ref
7E4F4BC5
Skor
100/100
Mode
Evidence v1

PhishDestroy first recorded luhkas.com on Oct 13, 2025. This English evidence brief is rebuilt from the current structured observations stored for the report. The current evidence score, computed from those stored observations, is 100/100.

The latest stored availability state is “Last known active” (HTTP 200) on Aug 3, 2026 at 22:26 UTC. This is a reachability snapshot, not proof of the cause of any outage, restriction, or status change.

VirusTotal returned 13 detections from 91 scanners in the stored check on Jul 26, 2026 at 02:48 UTC. The independent blocklist snapshot recorded 0 matches across 10 configured external sources on Aug 3, 2026 at 22:20 UTC. PhishDestroy's own listing is excluded from that count. A zero-match snapshot is not a safety verdict.

Other stored evidence. Google Safe Browsing stored no positive flag on Mar 3, 2026 at 04:14 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 0 pulse references on Mar 1, 2026 at 20:33 UTC. OTX pulses are community-intelligence references, not vendor verdicts. The Spamhaus DBL snapshot stored no positive result on Jul 14, 2026 at 18:37 UTC. That result is not evidence of safety. A URLScan capture is stored from Mar 4, 2026 at 22:10 UTC.

Stored context lists registrar PDR Ltd. d/b/a PublicDomainRegistry.com, IP address 104.21.34.38, registration date Sep 14, 2025, apparent target Genericcrypto. Except for the registration date, these fields do not share a source timestamp in this report and may change.

Treat these as stored, time-bound observations rather than a live safety guarantee. Source verdicts and reachability can change, and zero or missing vendor matches never prove that a domain is safe. Avoid interacting with the domain while uncertainty remains, and use the appeal process if this report is inaccurate.

VirusTotal
VirusTotal
13 det.
URLQuery
URLQuery
3 threat alerts
URLScan
URLScan
Gridinsoft
1/100
Sertifikat TLS
Kedaluwarsa atau belum diverifikasi -57d
Usia
11 mo
Status terpantau
Terakhir diketahui aktif 200
PhishDestroy
Daftar Hapus
Terdaftar
Reports Sent
14 ignored
Cakupan data VirusTotal 13 / 91 URLQuery 3 threat-system alerts OTX no community references CF Radar scan completed URLScan capture laporan yang disimpan URLScan verdict malicious Pemblokiran DNS tidak diperiksa TLS Kedaluwarsa atau belum diverifikasi WHOIS 11 mo old Tangkapan layar 3 captures · 3 sources Rantai pengalihan tidak diselidiki Gridinsoft 1/100
Sinyal Keamanan
GS Gridinsoft Analysis 1 / 100
Hosting SSL Certificate Scam - High Risk Amazon Phishing - High Risk Cryptocurrency Cryptocurrency - Risk Financial Service Registration Form
Intelijen Keamanan Jaringan
Threat Detection Systems 3 alerts
Detection System Indicator Verdict Alert
Hagezi Threat Feed luhkas.com malicious Sinkholed
OpenDNS luhkas.com phishing Phishing Block
DNS4EU luhkas.com malicious Sinkholed

Alur Tanggapan Ancaman Pipeline

Penemuan
Checks
Reports
Ketersediaan
28/29
Initial Abuse Report (#1)
Sent to 1 abuse contact at PDR Ltd. d/b/a PublicDomainRegistry.com with forensic evidence
abuse-contact@publicdomainregistry.com
03/02/2026
Follow-up Report #2
Escalation #2 sent to 1 recipient — follow-up record after a previous report
abuse-contact@publicdomainregistry.com
05/02/2026
Follow-up Report #3
Escalation #3 sent to 1 recipient — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.com
08/02/2026
ICANN Escalation #4
Escalation #4 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.comabuse@verisign-grs.comcompliance@icann.org
14/02/2026
ICANN Escalation #5
Escalation #5 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.comabuse@verisign-grs.comcompliance@icann.org
14/02/2026
ICANN Escalation #6
Escalation #6 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.comabuse@verisign-grs.comcompliance@icann.org
26/02/2026
ICANN Escalation #7
Escalation #7 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.comabuse@verisign-grs.comcompliance@icann.org
06/03/2026
ICANN Escalation #8
Escalation #8 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.comabuse@verisign-grs.comcompliance@icann.org
16/03/2026
ICANN Escalation #9
Escalation #9 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.comabuse@verisign-grs.comcompliance@icann.org
05/04/2026
ICANN Escalation #10
Escalation #10 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.comabuse@verisign-grs.comcompliance@icann.org
20/04/2026
ICANN Escalation #11
Escalation #11 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.comabuse@verisign-grs.comcompliance@icann.org
22/04/2026
ICANN Escalation #12
Escalation #12 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.comabuse@verisign-grs.comcompliance@icann.org
26/04/2026
ICANN Escalation #13
Escalation #13 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.comabuse@verisign-grs.comcompliance@icann.org
28/04/2026
ICANN Escalation #14
Escalation #14 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.comabuse@verisign-grs.comcompliance@icann.org
07/05/2026
14 Reports Filed
14 report records were stored over 181 days; current observed status: Terakhir diketahui aktif

Status Daftar Blokir Publik

Tangkapan tersimpan

Judul Halaman
Luhkas: Most Popular Online Crypto Casino Based on Blockchain
Sertifikat TLS
Kedaluwarsa atau belum diverifikasi · Diterbitkan oleh Google Trust Services / WE1

Intelijen Domain

Domain
URLScan Verdict Berbahaya score 100 report ↗
Server / ASN cloudflare · AS13335 CLOUDFLARENET, US
IP Context Cloudflare shared edge origin IP hidden Reputasi Edge-IP tidak dikaitkan dengan domain ini.
Alamat IP 104.21.34.38 CDN
LokasiUS San Francisco, US
JaringanAS13335 · Cloudflare, Inc.
IP asal tersembunyi di balik proksi CDN. Hasil IP terbalik untuk alamat edge berisi penyewa yang tidak terkait; menemukan asal memerlukan DNS pasif atau data transparansi sertifikat.
PendaftaranDibuat 14/09/2025 (323d) Expires 14/09/2026
Elapsed Since First Report 27 days
Yang kami hitung Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Terakhir diketahui aktif.
Minimum notice count 14 is the number of stored outgoing report records for this domain. It does not by itself prove acknowledgement or action by a recipient.
Isi setiap laporan Catatan laporan keluar yang disimpan dapat merujuk pada bukti yang tersedia pada saat itu, seperti keputusan vendor, data pendaftaran, detail hosting, klasifikasi, atau tangkapan layar. Halaman ini tidak menyimpulkan secara pasti muatan yang dikirimkan, penerimaan, pengakuan, atau tindakan oleh penerima.
ICANN RAA §3.18 The history below lists stored escalation records and timestamps. It does not by itself establish receipt, acknowledgement, compliance, or enforcement by any recipient.
Status HTTP200
Rincian teknisDNS, SAN SSL, cap waktu
Pertama Kali Terdeteksi13/10/2025
Submitted URLhttps://luhkas.com/
Server namaaiden.ns.cloudflare.comkim.ns.cloudflare.com
TLS Fingerprint
Favicon Hash
Case ID
ICANN OVERSIGHT

Akreditasi dan konteks RAA

ICANN Sudah Dibayar. Akuntabilitas Tak Kunjung Datang.

Untuk gTLD ini, registrar di atas beroperasi berdasarkan kontrak dengan ICANN. ICANN memungut biaya tahunan, biaya variabel, dan biaya berbasis transaksi yang terkait dengan pendaftaran, perpanjangan, dan transfer.

Akreditasi: dimonetisasi. Akuntabilitas: silakan periksa kembali nanti.

Lalu keajaiban dimulai: ICANN menulis RAA §3.18, registrar menyelidiki penyalahgunaan di dalam basis pelanggannya sendiri, dan para korban menyerahkan bukti secara cuma-cuma sementara setiap lapisan menunggu pihak lain bertindak. Jika itu membuat para korban merasa lebih aman, bagus sekali—ternyata tagihannya bekerja.

Catatan satir tentang akuntabilitas Tidak ada yang dikirim secara otomatis.
Riwayat Laporan Penyalahgunaan · 14 stored reports over 93 days · click to expand
This timeline is built from stored outgoing report records. It documents timestamps and listed recipients, but does not by itself prove delivery, acknowledgement, or recipient action.
14 abuse reports filed over 181 days — latest observed status: Terakhir diketahui aktif
The records name PDR Ltd. d/b/a PublicDomainRegistry.com as a recipient or subject. ICANN Compliance appears in the recipient field for at least one record.
14
reports
181
days
ICANN CC
  1. Report #1 Feb 3, 2026 · 06:31 UTC
    Phishing Abuse Report: luhkas[.]com
    abuse-contact@publicdomainregistry.com
  2. Report #2 Escalation 55h still active Feb 5, 2026 · 13:36 UTC
    ESCALATION #2 (55h active): Phishing - luhkas[.]com
    abuse-contact@publicdomainregistry.com
  3. Report #3 Escalation 131h still active Feb 8, 2026 · 18:29 UTC
    ESCALATION #3 (131h active): Phishing - luhkas[.]com
    abuse-contact@publicdomainregistry.com
  4. Report #4 ICANN CC 277h still active Feb 14, 2026 · 20:27 UTC
    ESCALATION #4 (277h active): Phishing - luhkas[.]com
    abuse-contact@publicdomainregistry.com abuse@verisign-grs.com compliance@icann.org
  5. Report #5 ICANN CC 280h still active Feb 14, 2026 · 23:08 UTC
    ESCALATION #5 (280h active): Phishing - luhkas[.]com
    abuse-contact@publicdomainregistry.com abuse@verisign-grs.com compliance@icann.org
  6. Report #6 ICANN CC 564h still active Feb 26, 2026 · 18:56 UTC
    ESCALATION #6 (564h active): Phishing - luhkas[.]com
    abuse-contact@publicdomainregistry.com abuse@verisign-grs.com compliance@icann.org
  7. Report #7 ICANN CC 748h still active Mar 6, 2026 · 10:50 UTC
    ESCALATION #7 (748h active): Phishing - luhkas[.]com
    abuse-contact@publicdomainregistry.com abuse@verisign-grs.com compliance@icann.org
  8. Report #8 ICANN CC 1001h still active Mar 16, 2026 · 23:30 UTC
    ESCALATION #8 (1001h active): Phishing - luhkas[.]com
    abuse-contact@publicdomainregistry.com abuse@verisign-grs.com compliance@icann.org
  9. Report #9 ICANN CC 1457h still active Apr 5, 2026 · 02:40 UTC
    ESCALATION #9 (1457h active): Phishing - luhkas[.]com
    abuse-contact@publicdomainregistry.com abuse@verisign-grs.com compliance@icann.org
  10. Report #10 ICANN CC 1829h still active Apr 20, 2026 · 14:33 UTC
    ESCALATION #10 (1829h active): Phishing - luhkas[.]com
    abuse-contact@publicdomainregistry.com abuse@verisign-grs.com compliance@icann.org
  11. Report #11 ICANN CC 1882h still active Apr 22, 2026 · 20:23 UTC
    ESCALATION #11 (1882h active): Phishing - luhkas[.]com
    abuse-contact@publicdomainregistry.com abuse@verisign-grs.com compliance@icann.org
  12. Report #12 ICANN CC 1975h still active Apr 26, 2026 · 17:09 UTC
    ESCALATION #12 (1975h active): Phishing - luhkas[.]com
    abuse-contact@publicdomainregistry.com abuse@verisign-grs.com compliance@icann.org
  13. Report #13 ICANN CC 2024h still active Apr 28, 2026 · 18:17 UTC
    ESCALATION #13 (2024h active): Phishing - luhkas[.]com
    abuse-contact@publicdomainregistry.com abuse@verisign-grs.com compliance@icann.org
  14. Report #14 ICANN CC 2223h still active May 7, 2026 · 01:11 UTC
    ESCALATION #14 (2223h active): Phishing - luhkas[.]com
    abuse-contact@publicdomainregistry.com abuse@verisign-grs.com compliance@icann.org
Record scope: the timeline documents outgoing records stored by PhishDestroy. Delivery, acknowledgement, and subsequent action require separate recipient or infrastructure evidence.
Laporkan Domain Ini Kirimkan bukti & bantu lindungi orang lain

Analisis VirusTotal

13 / Vendor keamanan 91 menandai domain ini
View on VT
ADMINUSLabs
alphaMountain.ai
BitDefender
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
SOCRadar
Sophos
VIPRE

Bukti Terarsip

Wayback Machine Snapshot
Cuplikan sejarah tersedia untuk tinjauan bukti
View Archive

Bukti & Laporan Eksternal

Apakah Anda Terpengaruh oleh Situs Ini?

Kamu tidak sendirian dan tidak ada yang perlu kamu malu-malui. Penipu adalah para penjahat yang cerdik dan memanfaatkan kepercayaan orang lain. Melaporkan pengalaman Anda adalah senjata paling ampuh untuk melawan penipuan — laporan Anda dapat mencegah orang lain menjadi korban dan membantu aparat penegak hukum mengambil tindakan. Diam adalah keunggulan terbesar para penipu. Hancurkan saja.

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.

Europol
Temukan saluran pelaporan resmi untuk negara UE Anda
National police directory
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
Draf yang dibantu AI — detail insiden diproses oleh penyedia AI Tinjau dan kirimkan sendiri

Tentang Laporan Ini: luhkas.com

Laporan ini menyajikan bukti tersimpan terbaru yang tersedia untuk PhishDestroy. Stempel waktu sumber ditampilkan jika tersedia; ketersediaan dan keputusan vendor dapat berubah setelah pengumpulan.

Situs yang diambil menampilkan judul halaman “Luhkas: Most Popular Online Crypto Casino Based on Blockchain” dan mungkin meniru identitas Genericcrypto.

Pada 04/08/2026, luhkas.com memiliki deteksi dari mesin keamanan 13.

Jika Anda yakin daftar ini tidak akurat, mengajukan banding. Untuk mempelajari metodologi kami, kunjungi halaman pertanyaan umum.

Periksa Domain Apa Pun

Analisis ancaman menggunakan daftar blokir yang disimpan, WHOIS, DNS, dan bukti pemindaian publik

Pindai Sekarang

Laporkan Phishing

Laporkan domain yang mencurigakan ke basis data ancaman kami — lindungi komunitas

Laporan

Pemberitahuan Ancaman Real-Time

Laporan phishing terbaru dan perubahan ketersediaan yang diamati

Pantau

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
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/luhkas.com"
  title="PhishDestroy threat report for luhkas.com"
  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>

Surat Terima Kasih yang Sangat Tulus

Pembuat draf satir

Penerima
Konteks biaya

Draf satir. Angka biaya merupakan perkiraan; tidak diklaim bahwa angka tersebut secara tepat terkait dengan domain ini.