VirusTotal
10 / 92 engine detections
Buka laporan“WhatsApp Profile Checker”
Peniruan Google: whatsapp.checkleaked.cc — Terakhir diketahui aktif (HTTP 200). Ringkasan bukti: VirusTotal 10/92 (CyRadar, Forcepoint ThreatSeeker, Fortinet…
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
10 / 92 engine detections
Buka laporanno community references
Buka laporanprovider verdict: clean
Buka laporanNo threat flag
Buka laporanNo malicious flag
Buka laporanResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
whatsapp.checkleaked.cc is an impersonation phishing page that presents itself as a "WhatsApp Profile Checker". It targets WhatsApp users who fear their account or phone number has leaked. PhishDestroy first flagged it on 2026-09-24. When last checked on 2026-10-19, the site was still online with its content live.
The lure is fear. A page that promises to check whether your WhatsApp profile has leaked invites you to type in your phone number and whatever else it asks for. Fake checkers like this typically lead victims into handing over the six-digit WhatsApp registration code or a two-step verification PIN. Either one lets an attacker register the account on their own device, lock the owner out and message their contacts for money. Personal details entered on the page can also be reused for targeted scams. WhatsApp itself runs no third-party profile or leak checker, so any site offering one under the WhatsApp name is not legitimate.
On VirusTotal, 10 of 92 engines flagged the URL as of 2026-10-07. Among them are Fortinet, Forcepoint ThreatSeeker, Gridinsoft, CyRadar, Lionic, SafeToOpen, SOCRadar and URLQuery. That is a minority of engines, but it is a spread of independent vendors that agree with our classification. Besides PhishDestroy, the Phishunt blocklist also lists the domain.
The parent domain checkleaked.cc was registered through NameCheap, Inc. on 2020-11-26, nearly six years before the WhatsApp-themed subdomain reached our blocklist. Its name is generic enough that it could carry checkers styled after other brands as well. Traffic resolves to Cloudflare, Inc. (104.26.3.249, located in CA), which hides the real origin server behind a shared proxy.
If you entered your phone number, watch for unexpected WhatsApp verification codes and never share one with anyone. If you typed in a code or your PIN, reopen WhatsApp right away and re-verify your number to push out any intruder. Then turn on two-step verification with a new PIN and check Linked Devices for sessions you don't recognize. Warn your contacts so they ignore any money requests sent in your name. Defenders should block the checkleaked.cc domain and its subdomains, and report the page to Cloudflare and NameCheap abuse teams.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/WhatsappNumberSearch_botStored page referenceIoC extraction recorded 2026-09-25 04:00:20 UTC
Last checked
Reputasi Edge-IP tidak dikaitkan dengan domain ini.
gordon.ns.cloudflare.comroute1.mx.cloudflare.netpriority 11route2.mx.cloudflare.netpriority 44route3.mx.cloudflare.netpriority 84Location describes the IP network.
9858885a3d4c072c7da32e5e1920704c35bb1bda39dc3ce4d6a806095a7a643bcheckleaked.ccSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of whatsapp.checkleaked.cc · checked Sep 24, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
whatsapp.checkleaked.cc
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Dapat dijangkau→Tidak tersedia
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak tersedia→Dapat dijangkau
Dapat dijangkau→Tidak tersedia
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
9→8
8→9
No threat flag
View source10/92 engine detections
View sourcewhatsapp.checkleaked.cc
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
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.
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
whatsapp.checkleaked.cc)Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Analisis ancaman menggunakan daftar blokir yang disimpan, WHOIS, DNS, dan bukti pemindaian publik
Pindai SekarangLaporkan domain yang mencurigakan ke basis data ancaman kami — lindungi komunitas
LaporanLaporan phishing terbaru dan perubahan ketersediaan yang diamati
PantauPantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive
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.