Lompat ke laporan keamanan
Keamanan domain dan intelijen ancaman
jalebinspice.com favicon

jalebinspice.com

“RFP Invitation”

Registrar
NameCheap
Resolved IP
67.223.118.123
Registered
06/05/2024
PhishDestroy assessment Kritis
Ketersediaan Terakhir diketahui aktif Pengamatan keterjangkauan tersimpan terbaru Teramati · HTTP probe
Deteksi Total Virus: 8/91 Jenis penipuan: Impersonation
OTX: 4 refs 17/09/2026
API
Domain ini telah ditandai sebagai berbahaya
Mesin keamanan melaporkan deteksi: 8. Berhati-hatilah — jangan memasukkan kredensial atau informasi pribadi.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Ringkasan laporan

Phishing: jalebinspice.com — Terakhir diketahui aktif (HTTP 200). Ringkasan bukti: VirusTotal 8/91 (alphaMountain.ai, CRDF, ESET, Forcepoint ThreatSeeker…

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

Source evidenceVirusTotal 8 / 91 · OTX 4 references 6 sources

VirusTotal

8 / 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
8 / 91
OTX
4 community refs
Page captures
2

PhishDestroy threat report

Overview

jalebinspice.com hosts an impersonation phishing page titled "RFP Invitation", built to look like a legitimate request for proposal sent to suppliers and contractors. Its targets are business users, especially people in sales, procurement and finance who routinely receive bid invitations. PhishDestroy first flagged it on 2026-09-17, and as of 2026-10-19 the site was still online and serving its phishing content.

How the scam works

RFP lures usually arrive by email as an invitation to review tender documents or submit a bid. The link leads to a page like this one, which asks the visitor to sign in with a work email account to view the files. Whatever is typed in goes to the operators, who can use the mailbox to read correspondence, launch invoice or payment-redirection fraud, and send the same lure to the victim's contacts from a trusted address.

Evidence

On 2026-09-29, 8 of 91 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, ESET, Forcepoint ThreatSeeker, Gridinsoft, MalwareURL, SOCRadar and VIPRE. That is a modest but meaningful spread across independent vendors, so many filters will still let it through. The domain also appears in 4 AlienVault OTX threat pulses, which shows other researchers have linked it to malicious activity, and it is listed on the PhishDestroy blocklist.

Infrastructure

The domain was registered through NameCheap, Inc. on 2024-05-06, more than two years before it was seen hosting this lure. An older domain like this gets past filters that treat newly registered names with suspicion, and the name itself has nothing to do with procurement. It resolves to 67.223.118.123 on Namecheap, Inc. hosting in the US. Its Let's Encrypt certificate gives the page a browser padlock, but that only shows the connection is encrypted, not that the site is trustworthy.

What to do

If you entered a password on this page, change it right away, along with any other account that uses the same password, and turn on two-factor authentication. Sign out all active sessions. Check your mailbox for new forwarding rules, filters or app authorizations you did not create, and warn your contacts not to trust recent RFP or invoice emails sent from your address. Security teams should block the domain and its IP, search mail logs for messages linking to it, and reset credentials for any user who clicked through.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Tangkapan tersimpan · 2 captures

Domain details

Domain
URLScan verdict Analisis selesai score 0 report ↗
Reputasi IP abuse score 0/100 0 reports checked 17/10/2026
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomaindrainerfraudmonthlyphishdestroyphishingscam
Registrar NameCheap US(US)
Kontak penyalahgunaan["abuse@namecheap.com"]
PendaftaranDibuat 06/05/2024 — Expires 06/05/2027
Status HTTP200
Detail teknisProvenance & timestamps
Pertama Kali Terdeteksi17/09/2026
DOM Analysisanalyzed 17/09/2026score 88/100
Submitted URLhttp://jalebinspice.com/umt
Favicon Hash
Observed page title
RFP Invitation
Sertifikat TLS
Diterbitkan oleh Let's Encrypt / YE2 · stored validity ends in 39 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
67.223.118.123
Network ASN
AS22612
Organization
Namecheap, Inc
Observed location
Chicago, US
Server header
LiteSpeed

Server nama 1

  • dns2.namecheaphosting.com

Mail routing 3 MX records

  • mx1-hosting.jellyfish.systemspriority 5
  • mx2-hosting.jellyfish.systemspriority 10
  • mx3-hosting.jellyfish.systemspriority 20

Location describes the IP network.

Sertifikat TLS

Issuer
Let's Encrypt / YE2
Valid from
2026-08-31 11:47:13
Valid until
2026-11-29 11:47:12
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-17 10:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprintbf271c1c01b82cd612557433b2ebb6d3e1989387925eeeb9ced4448713cad565
Certificate names · 2 SANs
  • mail.jalebinspice.com
  • www.jalebinspice.com

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-19 22:30:06 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-19 22:30:06 UTC
RDAP registration Tidak diketahui
Observed timeline last reachable: 2026-10-19 22:35:33 UTC last content: 2026-10-19 22:30:06 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.
Recorded subdomains2

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

  • mail.jalebinspice.comDomain record
  • www.jalebinspice.comDomain record

The original observation time is not recorded for these hostnames.

Teknologi · 12 identified
Detected via Cloudflare Radar · Wappalyzer engine
Laporkan Domain Ini Kirimkan bukti & bantu lindungi orang lain

Analisis VirusTotal

8 / Vendor keamanan 91 menandai domain ini
View on VT
Last analyzed Previous stored snapshot: 7 detections
alphaMountain.ai
CRDF
ESET
Forcepoint ThreatSeeker
Gridinsoft
MalwareURL
SOCRadar
VIPRE

Bukti Terarsip

Wayback Machine Snapshot
Cuplikan sejarah tersedia untuk tinjauan bukti
View Archive
Analisis Performa Situs

Google PageSpeed Insights — mobile performance audit of jalebinspice.com · checked Sep 17, 2026

54
Needs Work
Performance
FCP
3.91s
First Contentful Paint
LCP
18.6s
Largest Contentful Paint
CLS
0.125
Cumulative Layout Shift
TBT
99ms
Total Blocking Time
SI
10.14s
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.

Check for cloaking

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

Page titles differ

alive_content: raw=ok; http=200; via=https_proxy; server=LiteSpeed

Browser
RFP Invitation
Crawler
Jalebi N Spice – Get it delivered right to your door
jalebinspice.com
Hasil tersimpan
Cloaked / Filtered
Stored observation history19

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

    redirected→live_content

    content_served

  7. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  8. Availability monitor · Recorded state

    live_content→redirected

    http_redirect

  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. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

Recorded activity

4 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    8/91 engine detections

    View source
  4. Added to PhishDestroy

    jalebinspice.com

    View source

Bukti & Laporan Eksternal

Analisis Mendalam
Help & reporting

Apakah Anda Terpengaruh oleh Situs Ini?

5 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 jalebinspice.com)
  • 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/jalebinspice.com"
  title="PhishDestroy threat report for jalebinspice.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>