Why this matters — ICANN RAA §3.18 obligation & victim-assistance
On PhishDestroy delivered an evidence-backed abuse report
(repeated 9 times, most recently ) to abuse@inwx.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 INWX GmbH doesn't consider the listed detections enough proof — that is interesting in itself, given the volume of independent vendor confirmations. But after 9 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.
stakeup[.]com
Pemeriksaan phishing dan keamanan stakeup.com
“StakeUp”
stakeup.com: 4 dari 95 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.
PhishDestroy first recorded stakeup.com on Dec 1, 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 77/100.
The latest stored availability state is “Last known active” (HTTP 200) on Aug 2, 2026 at 10:46 UTC. This is a reachability snapshot, not proof of the cause of any outage, restriction, or status change.
VirusTotal returned 4 detections from 95 scanners in the stored check on Jul 12, 2026 at 17:21 UTC. The independent blocklist snapshot recorded 0 matches across 10 configured external sources on Aug 2, 2026 at 14: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 Jul 12, 2026 at 17:22 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 23 pulse references on Jul 12, 2026 at 17:22 UTC. OTX pulses are community-intelligence references, not vendor verdicts. The Spamhaus DBL snapshot stored no positive result on Jul 14, 2026 at 14:37 UTC. That result is not evidence of safety. A URLScan capture is stored from Feb 27, 2026 at 01:28 UTC.
Stored context lists registrar INWX GmbH, IP address 185.181.105.76, registration date Dec 14, 2006. 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.
Intelijen Keamanan Jaringan
Alur Tanggapan Ancaman Pipeline
Status Daftar Blokir Publik
Stored Capture
Intelijen Domain
Rincian teknisDNS, SAN SSL, cap waktu
ICANN OVERSIGHT
Akreditasi dan konteks RAA
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.
Riwayat Laporan Penyalahgunaan · 9 stored reports over 110 days · click to expand
-
Report #1 Feb 3, 2026 · 06:31 UTCPhishing Abuse Report: stakeup[.]comabuse@inwx.com
-
Report #2 Escalation 55h still active Feb 5, 2026 · 13:36 UTCESCALATION #2 (55h active): Phishing - stakeup[.]comabuse@inwx.com
-
Report #3 ICANN CC 715h still active Mar 5, 2026 · 01:53 UTCESCALATION #3 (715h active): Phishing - stakeup[.]comabuse@inwx.com abuse@verisign-grs.com compliance@icann.org
-
Report #4 ICANN CC 749h still active Mar 6, 2026 · 11:35 UTCESCALATION #4 (749h active): Phishing - stakeup[.]comabuse@inwx.com abuse@verisign-grs.com compliance@icann.org
-
Report #5 ICANN CC 1882h still active Apr 22, 2026 · 20:19 UTCESCALATION #5 (1882h active): Phishing - stakeup[.]comabuse@inwx.com abuse@verisign-grs.com compliance@icann.org
-
Report #6 ICANN CC 1975h still active Apr 26, 2026 · 17:10 UTCESCALATION #6 (1975h active): Phishing - stakeup[.]comabuse@inwx.com abuse@verisign-grs.com compliance@icann.org
-
Report #7 ICANN CC 2024h still active Apr 28, 2026 · 18:21 UTCESCALATION #7 (2024h active): Phishing - stakeup[.]comabuse@inwx.com abuse@verisign-grs.com compliance@icann.org
-
Report #8 ICANN CC 2182h still active May 5, 2026 · 08:25 UTCESCALATION #8 (2182h active): Phishing - stakeup[.]comabuse@inwx.com abuse@verisign-grs.com compliance@icann.org
-
Report #9 ICANN CC 2636h still active May 24, 2026 · 06:24 UTCESCALATION #9 (2636h active): Phishing - stakeup[.]comabuse@inwx.com abuse@verisign-grs.com compliance@icann.org
Casino / Gambling License Verification
Analisis VirusTotal
Bukti Terarsip
Analisis Performa Situs
Google PageSpeed Insights — mobile performance audit of stakeup.com · checked Jul 12, 2026
Bukti & Laporan Eksternal
Apakah Anda Terpengaruh oleh Situs Ini?
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.
Laporkan kepada Pihak Berwenang di Daerah Anda
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
Tentang Laporan Ini: stakeup.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 “StakeUp”.
Pada 02/08/2026, stakeup.com memiliki deteksi dari mesin keamanan 4.
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 SekarangLaporkan Phishing
Laporkan domain yang mencurigakan ke basis data ancaman kami — lindungi komunitas
LaporanPemberitahuan Ancaman Real-Time
Laporan phishing terbaru dan perubahan ketersediaan yang diamati
PantauTetap Terinformasi, Tetap Aman
Pantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive