Lompat ke laporan keamanan
Keamanan domain dan intelijen ancaman
facebook-case-business.com favicon

facebook-case-business.com

“404: NOT_FOUND”

Registrar
Cloudflare
Resolved IP
216.198.79.65
Registered
15/09/2026
PhishDestroy assessment Kritis
Ketersediaan Terakhir diketahui aktif Sebelumnya tidak tersedia; observasi terbaru dapat dicapai Teramati · HTTP probe
Deteksi Total Virus: 18/91 Spamhaus DBL: DBL_PHISH Label merek otomatis: Facebook Google Safe Browsing: threat flag recorded
OTX: 4 refs 17/09/2026 CDN
API
Domain ini telah ditandai sebagai berbahaya
Mesin keamanan melaporkan deteksi: 18. Berhati-hatilah — jangan memasukkan kredensial atau informasi pribadi.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Domain age
Ringkasan laporan

Peniruan Facebook: facebook-case-business.com — Terakhir diketahui aktif (HTTP 308). Ringkasan bukti: VirusTotal 18/91 (alphaMountain.ai, BitDefender, CRDF…

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

Source evidenceVirusTotal 18 / 91 · Google Safe Browsing: flagged · OTX 4 references 6 sources

VirusTotal

18 / 91 engine detections

Buka laporan

Google Safe Browsing

Threat flag recorded

Buka laporan

Spamhaus DBL

DBL_PHISH

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Intelijen Keamanan Jaringan
CF Cloudflare Radar Verdict Berbahaya
Malware Security Risks Security threats Malware

Analysis

Kritis
VirusTotal
18 / 91
OTX
4 community refs

PhishDestroy threat report

Overview

facebook-case-business.com is a phishing domain that impersonates Facebook. Its name targets business page owners and advertisers by suggesting an official "case" or support process. PhishDestroy first flagged it on 2026-09-17. As of 2026-10-19 the site was still online and its content returned a redirect rather than a page of its own.

How the scam works

Domains built like this usually support a familiar Facebook lure. The victim gets a message claiming their page or ad account has a policy violation, copyright complaint or pending case, and is told to file an appeal before the account is disabled. The appeal form asks for the Facebook login, password and often the two-factor code, which hands the attacker control of the account, its pages and any linked ad spend. When we checked, the page title read "404: NOT_FOUND", while our classification is Facebook impersonation phishing.

Evidence

On 2026-09-25, 18 of 91 VirusTotal engines flagged the domain as malicious. They include BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, alphaMountain.ai, CRDF and CyRadar. Agreement across that many separate vendors is strong support for the phishing verdict. Google Safe Browsing lists the domain under SOCIAL_ENGINEERING, and Spamhaus DBL classifies it as DBL_PHISH. It also appears in four AlienVault OTX threat pulses and on the PhishDestroy blocklist.

Infrastructure

The domain was registered on 2026-09-15 through Cloudflare, Inc., only two days before PhishDestroy detected it. That short gap fits a campaign domain created for immediate use. It resolves to 216.198.79.65 on Amazon.com, Inc. infrastructure in the US. Its Let's Encrypt certificate means the browser padlock appears, so the padlock alone does not show the site is genuine.

What to do

If you entered your Facebook credentials on this site, change your password right away from the official app or site. Log out of all other sessions, and reset two-factor authentication if you typed in a code. Under Facebook's security settings, check Business Manager admins, page roles, linked emails and ad payment methods for anything you did not add. Facebook does not open policy cases on outside domains, so treat any message pointing you elsewhere as phishing. Defenders should block the domain at DNS and the mail gateway, search mail logs for messages linking to it, and reset credentials for any staff who clicked.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Domain details

Domain
Google Safe Browsing Ditandai Social engineering checked 25/09/2026
IP Context Vercel shared edge origin IP hidden Reputasi Edge-IP tidak dikaitkan dengan domain ini.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomaindrainerfraudmonthlyphishdestroyphishingscam
Registrar Cloudflare US(US)
PendaftaranDibuat 15/09/2026 (34d · New) — Expires 15/09/2027
Status HTTP308 Permanent Redirect
Elapsed Since First Report 32 days
Yang kami hitung Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Terakhir diketahui aktif.
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 Terdeteksi17/09/2026
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
216.198.79.65
Network ASN
AS16509
Organization
CYPRESS COMMUNICATIONS, LLC
Observed location
Cleveland, US
Server header
Vercel

Reputasi Edge-IP tidak dikaitkan dengan domain ini.

Server nama 1

  • hasslo.ns.cloudflare.com

Location describes the IP network.

Sertifikat TLS

Issuer
Let's Encrypt / YR1
Valid from
2026-09-15 15:26:56
Valid until
2026-12-14 15:26:55
Validity
Within stored validity dates
Collection time
2026-10-11 04:03:22 UTC
Collection source
PhishDestroy collector
Certificate fingerprintdb64e89401d8c662fe58d66a4bbeb1ea39edc54860fa8be548a3ccadf67f9a08

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:58 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-19 22:34:58 UTC
RDAP registration Tidak diketahui
Observed timeline last reachable: 2026-10-19 22:34:58 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.
Teknologi · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Laporkan Domain Ini Kirimkan bukti & bantu lindungi orang lain

Analisis VirusTotal

18 / Vendor keamanan 91 menandai domain ini
View on VT
Last analyzed First positive detection Previous stored snapshot: 18 detections
alphaMountain.ai
BitDefender
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
Kaspersky
LevelBlue
MalwareURL
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Registration & observation details2

Availability observations

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

Stored observation history27

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

    Tidak diketahui→redirected

    http_redirect

  3. Availability monitor · Recorded state

    protected→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Tidak diketahui→protected

    http_access_restricted · access_restriction

  5. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

Earlier observations 22
  1. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Tidak tersedia→Dapat dijangkau

  4. Availability monitor · Recorded state

    Dapat dijangkau→Tidak tersedia

  5. Availability monitor · Recorded state

    Tidak diketahui→protected

    http_access_restricted · access_restriction

  6. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  7. Availability monitor · Recorded state

    protected→redirected

    http_redirect

  8. Availability monitor · Recorded state

    Tidak diketahui→protected

    http_access_restricted · access_restriction

  9. Availability monitor · Recorded state

    redirected→protected

    http_access_restricted · access_restriction

  10. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  11. Availability monitor · Recorded state

    redirected→protected

    http_access_restricted · access_restriction

  12. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  13. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  14. Availability monitor · Recorded state

    Tidak tersedia→Dapat dijangkau

  15. Availability monitor · Recorded state

    Tidak diketahui→inactive

    http_no_content

  16. Availability monitor · Recorded state

    Tidak diketahui→inactive

    http_no_content

  17. Availability monitor · Recorded state

    Tidak diketahui→inactive

    http_no_content

  18. VirusTotal · Detection count

    17→18

  19. Availability monitor · Recorded state

    https://radar.cloudflare.com/scan/a2941dea-4ebb-4e11-bcec-ba453d34c25b

  20. Availability monitor · Recorded state

    Dapat dijangkau→Tidak tersedia

  21. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  22. Availability monitor · First collection record

    Dapat dijangkau

Recorded activity

4 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Google Safe Browsing

    Threat flag recorded

    View source
  3. VirusTotal

    18/91 engine detections

    View source
  4. Added to PhishDestroy

    facebook-case-business.com

    View source

Check for cloaking

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

facebook-case-business.com

Bukti & Laporan Eksternal

Analisis Mendalam
Help & reporting

Apakah Anda Terpengaruh oleh Situs Ini?

3 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 facebook-case-business.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/facebook-case-business.com"
  title="PhishDestroy threat report for facebook-case-business.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>