Lompat ke laporan keamanan
Keamanan domain dan intelijen ancaman
engaigeobesity.bgbx.net favicon

engaigeobesity.bgbx.net

“EngAIge - from interactions to insight”

Registrar
NameCheap
Resolved IP
185.158.133.1
Registered
04/08/2026
PhishDestroy assessment Kritis
Ketersediaan Konten tidak tersedia Konten tidak tersedia dalam observasi terbaru Teramati · HTTP probe
Deteksi Total Virus: 11/92 Label merek otomatis: Google
04/09/2026 CDN
API
Domain ini telah ditandai sebagai berbahaya
Mesin keamanan melaporkan deteksi: 11. Berhati-hatilah — jangan memasukkan kredensial atau informasi pribadi.
VirusTotal
engine detections
Google Safe Browsing
Domain age
Ringkasan laporan

Peniruan Google: engaigeobesity.bgbx.net — Konten tidak tersedia (HTTP 404). Ringkasan bukti: VirusTotal 11/92 (alphaMountain.ai, BitDefender, CRDF…

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

Source evidenceVirusTotal 11 / 92 4 sources

VirusTotal

11 / 92 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
11 / 92

PhishDestroy threat report

Overview

engaigeobesity.bgbx.net is an impersonation phishing page that presents itself as EngAIge, carrying the page title "EngAIge - from interactions to insight". It targets people who know or use the EngAIge brand, and the hostname pairs the brand name with an unrelated word on a bgbx.net subdomain. PhishDestroy first flagged it on 2026-09-04. As of 2026-10-19 the site was still online and redirecting visitors elsewhere.

How the scam works

Impersonation pages borrow a real company's name, tagline and look so the visitor assumes they are on the genuine service. Once that trust is in place, the page asks for something valuable, usually a login, email address, contact details or a payment step, and passes it to the operators. Here the EngAIge tagline does the persuading. Because the site currently redirects, a visitor may land on a different page than the one first seen, and that page can serve the same lure.

Evidence

On 2026-10-19, 11 of 92 VirusTotal engines marked the domain as malicious. The flagging vendors were alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky, so the verdict comes from several independent security companies. PhishDestroy lists the domain on its own blocklist. Most engines have not flagged it yet, so a clean result in a browser or filter does not mean the site is safe.

Infrastructure

The domain was registered through NameCheap, Inc. on 2026-08-04, one month before PhishDestroy detected it. A domain that new imitating an established brand fits the pattern of a short-lived phishing setup. The site sits behind Cloudflare, Inc. on an address located in Germany, which hides the actual origin server.

What to do

If you entered an EngAIge password or any other login on this site, change it at once on the real service and on every account that reuses it, then turn on two-factor authentication. Check your account for unfamiliar sessions or recent changes, and treat any follow-up email or call that mentions EngAIge with suspicion. If you gave card or payment details, contact your bank. Defenders should block the hostname and the bgbx.net parent at the DNS, proxy and mail gateway, and search logs for users who visited after 2026-09-04. Report the domain to the registrar and hosting provider so it can be taken down.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Domain details

Domain
IP Context Cloudflare shared edge origin IP hidden Reputasi Edge-IP tidak dikaitkan dengan domain ini.
Registrar (base domain) NameCheap US(US)
Kontak penyalahgunaan["abuse@namecheap.com"]
Registration (base domain)bgbx.net · Dibuat 04/08/2026 (77d · New) — Expires 04/08/2027
Status HTTP404 Not Found
Waktu hingga pertama kali tidak tersedia 45 days
Yang kami hitung Waktu yang berlalu sejak laporan penyalahgunaan pertama kali disimpan hingga pengamatan pertama bahwa konten tersebut tidak tersedia. Hal ini tidak dapat menentukan penyebabnya.
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.
Detail teknisProvenance & timestamps
Pertama Kali Terdeteksi04/09/2026
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
185.158.133.1
Network ASN
AS13335
Organization
DET FRA
Observed location
Frankfurt am Main, DE
Server header
cloudflare

Reputasi Edge-IP tidak dikaitkan dengan domain ini.

Server nama 1

  • alfred.ns.cloudflare.com

Location describes the IP network.

Sertifikat TLS

Issuer
Google Trust Services / WE1
Valid from
2026-09-03 12:00:46
Valid until
2026-12-02 13:00:42
Validity
Within stored validity dates
Collection time
2026-10-11 01:03:25 UTC
Collection source
PhishDestroy collector
Certificate fingerprintae0cab734624526e329ffbd43c92cbf2702f49b3abe95f3c3b601450b5440103

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:34:48 UTC

Primary outcome Tidak aktif reason: Http No Content 70% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Root path has no content Content: Absent At Root DNS: Resolved Registration: Unknown
Latest HTTP observation Tidak aktif Http No Content 70% 2026-10-19 22:34:48 UTC
RDAP registration Tidak diketahui
Observed timeline last reachable: 2026-10-19 10:35:21 UTC last content: 2026-10-08 10:18:12 UTC current episode first observed: 2026-10-19 22:34:48 UTC observed RIP window: 2026-10-19 10:35:21 UTC → 2026-10-19 22:34:48 UTC · 11.99h midpoint estimate ≈ 2026-10-19 16:35:04 UTC · precision medium · basis bounded
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.
Teknologi · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Laporkan Domain Ini Kirimkan bukti & bantu lindungi orang lain

Analisis VirusTotal

11 / Vendor keamanan 92 menandai domain ini
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
BitDefender
CRDF
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
SOCRadar
Sophos
Analisis Performa Situs

Google PageSpeed Insights — mobile performance audit of engaigeobesity.bgbx.net · checked Sep 14, 2026

68
Needs Work
Performance
FCP
2.92s
First Contentful Paint
LCP
6.76s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
31ms
Total Blocking Time
SI
5.22s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details9

Availability observations

Last reachable observation
Last content observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
11.99
Estimate basis
Bounded by observations
Estimate precision
Sedang

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

http_other: raw=http_404; http=404; via=http_proxy; server=cloudflare

Browser
EngAIge - from interactions to insight
Crawler
Project not found
engaigeobesity.bgbx.net
Stored observation history21

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

    Dapat dijangkau→Tidak tersedia

  2. Availability monitor · Recorded state

    redirected→inactive

    http_no_content

  3. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

Earlier observations 16
  1. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Tidak tersedia→Dapat dijangkau

  3. Availability monitor · Recorded state

    Dapat dijangkau→Tidak tersedia

  4. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  6. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  7. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  8. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  9. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  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

  15. VirusTotal · Detection count

    1→3

  16. Availability monitor · First collection record

    Dapat dijangkau

Recorded activity

3 entries
  1. VirusTotal

    11/92 engine detections

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. Added to PhishDestroy

    engaigeobesity.bgbx.net

    View source

Intelijen komunitas

1 laporan komunitas

KategoriPHISHING

The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-09-04T14:35:28.603Z.

Bukti & Laporan Eksternal

Third-Party Detection — ChainAbuse
1 report filed for engaigeobesity.bgbx.net · category: Phishing · source checked
Flagged by PhishFort Detection System on Sep 4, 2026 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
Analisis Mendalam
Help & reporting

Apakah Anda Terpengaruh oleh Situs Ini?

1 evidence signal groups linked 0 stored notification records Konten tidak tersedia

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 engaigeobesity.bgbx.net)
  • 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/engaigeobesity.bgbx.net"
  title="PhishDestroy threat report for engaigeobesity.bgbx.net"
  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>