Lompat ke laporan keamanan
Dasbor Analitik
Keamanan domain dan intelijen ancaman
aml-challenge.org favicon

aml-challenge.org

Registrar
Dynadot
Resolved IP
107.189.20.11
Registered
11/10/2026
PhishDestroy assessment Sedang
First observed Oct 20, 2026 20:23 UTC · PhishDestroy
Sinyal risiko
Daftar ancaman PhishDestroy yang tersimpan Domain muda: 9 berumur hari
20/10/2026 1 Report Sent
API
Suspicious Domain — Listed on PhishDestroy
Daftar ancaman PhishDestroy yang tersimpan. Berhati-hatilah — jangan memasukkan kredensial atau informasi pribadi.
Google Safe Browsing
No threat flag
Page captures
2
open gallery
Domain age
9 days
Reports sent
1
view timeline
Page analysis & latest checkschecked 2026-10-20 3 checks

Google Safe Browsing

No threat flag

Not on Google threat lists at check time

Open

AlienVault OTX

0

threat pulses mention the domain

Open

Site status

Online · HTTP 200

107.189.20.11 · TLS: Let's Encrypt

Reports received
1
First reported
2026-10-20 20:19 UTC
Terdaftar
2026-10-20 20:19 UTC
Reported by
PhishDestroy team
Basis for listing
Trusted reporter, confirmed by automated checks

Each check shows its own collection time. Zero detections do not guarantee safety.

Ringkasan laporan

aml-challenge.org — Belum terverifikasi. Ringkasan bukti: URLScan capture; PhishDestroy score 25/100. Registrar: Dynadot.

The evidence summary below uses retained observations. Each source keeps its own collection date.

Source evidence 3 sources

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.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Tangkapan tersimpan · 2 captures

Primary capture 1 / 2
SumberPrimary capture
Recorded2026-10-20 20:23 UTC
StateStored capture
HTTP status at archiveHTTP 200
Final URLhttps://aml-challenge.org/
Position1 / 2
Open capture Wayback Unduh

Domain details

Domain
Registrar Dynadot US(US)
Kontak penyalahgunaanabuse@dynadot.com, abuse-reports@cloudzy.com
Pendaftar ICANNICANN Lookup (RDAP) →
Pencarian WHOISICANN RDAP untuk aml-challenge.org →
PendaftaranDibuat 11/10/2026 (9d · Very New!) — Expires 11/10/2027
Detail teknisProvenance & timestamps
Pertama Kali Terdeteksi20/10/2026
Submitted URLhttps://aml-challenge.org/

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
107.189.20.11

Server nama 2

  • ns1.dyna-ns.net
  • ns2.dyna-ns.net
viewdns.info · 107.189.20.11rapiddns.io
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • api.aml-challenge.orgDomain record

The original observation time is not recorded for these hostnames.

Laporkan Domain Ini Kirimkan bukti & bantu lindungi orang lain
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: https://aml-challenge.org/
AMLBot - Comprehensive Crypto Compliance Solution | Free AML Crypto Check
AMLBot provides an advanced AML screening tool for crypto companies and end-users. Discover how Bitcoin and altcoins are connected with illicit activities and secure your wallets with our crypto checker bot.
Respons
HTTP 200
HTML body
141.4 KB
Compressed
39.6 KB
Links
26 internal · 16 external
Detected technologies
nginxreact
Selected response headers
Server: nginx/1.27.5
Content-Type: text/html; charset=utf-8
X-Powered-By: Next.js
Cache-Control: s-maxage=31536000
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 13
Cache-Control
s-maxage=31536000
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Tue, 20 Oct 2026 20:24:34 GMT
Etag
"1698d8ypj5633ou"
Server
nginx/1.27.5
Transfer-Encoding
chunked
Vary
rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding
x-nextjs-cache
HIT
x-nextjs-prerender
1
x-nextjs-stale-time
300
X-Powered-By
Next.js

Values retained by the collector; long values may be shortened during collection.

Archived
Registration & observation details1

Availability observations

Last reachable observation

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

Stored observation history1

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

  1. Availability monitor · First collection record

    Dapat dijangkau

Recorded activity

4 entries
  1. Abuse report sent

    PD-20261020-779460

    abuse@dynadot.com
  2. Added to PhishDestroy

    aml-challenge.org

    View source
  3. URLScan

    Page captured

    View source
  4. Google Safe Browsing

    No threat flag

    View source

Check for cloaking

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

aml-challenge.org

Bukti & Laporan Eksternal

Analisis Keamanan
URLScan Stored capture VirusTotal ChainPatrol URLQuery SSL Laboratorium WOT ScamAdviser Pemeriksa Daftar Hitam URLVoid Sucuri SiteCheck Observatorium MDN
Snapshot bukti yang dikirim
Sent: Ledger records: 1 Case ID: PD-20261020-779460 Recipient: abuse@dynadot.com
Page title stored with report: AMLBot - Comprehensive Crypto Compliance Solution | Free AML Crypto Check
PDF notice generated Notice text archived (291 chars)
Abuse notice text as sent to the provider 
Registrar: Dynadot LLC / Dynadot Inc (United States)
Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains
Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
OSINT & Intelijen
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Batu Hudson Sign-in search IntelX crt.sh Sertifikat WHOIS Wayback
DNS & Jaringan
nslookup.io DNS bgp.tools ASN /Rute
SEO & Domain
SpyFu Moz DA/PA Ahrefs Tautan balik
Analisis Mendalam
Analisis Mendalam
Help & reporting

Apakah Anda Terpengaruh oleh Situs Ini?

4 evidence signal groups linked 1 stored notification records Belum terverifikasi
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.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Bukan laporan penegakan hukum
Banding atas Nama Domain
Minta peninjauan jika Anda pemilik domain ini dan yakin cantumannya salah
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 aml-challenge.org)
  • 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

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
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.

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.

Request a correction or appeal How PhishDestroy works
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/aml-challenge.org"
  title="PhishDestroy threat report for aml-challenge.org"
  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>