VirusTotal
5 / 92 engine detections
Buka laporan“IndexFlow — URL İndeksleme, Reklam Kampanyası ve AI SEO Tema Üretici”
Peniruan Ethereum: indexflower.com — Terakhir diketahui aktif (HTTP 200). Ringkasan bukti: VirusTotal 5/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker…
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
5 / 92 engine detections
Buka laporan4 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
indexflower.com presents itself as IndexFlow, a Turkish-language service promising URL indexing, ad campaigns and an AI SEO theme generator. PhishDestroy classifies it as an impersonation phishing page aimed at site owners, SEO freelancers and digital marketers. We first flagged it on 2026-09-05, and as of 2026-10-19 the site was still online and serving its content. The page title advertises an SEO tooling service rather than anything financial, while our classification is impersonation phishing.
Impersonation pages like this borrow the name and look of a legitimate-sounding tool so visitors trust them with logins, payments or account access. An SEO and indexing pitch is a natural lure: to "index" URLs or run campaigns, victims are often asked to sign in, connect search-console or advertising accounts, or pay for credits up front. Anyone who complies can lose the credentials they typed, the money they paid, or control of the web and ad accounts they linked.
Five of 92 VirusTotal engines flag the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar, as checked on 2026-10-19. That is a modest count, but it comes from several unrelated reputation and threat-intel vendors rather than a single source. The domain also appears in four AlienVault OTX community pulses. Beyond our own blocklist, it is not yet listed on other major blocklists, so many browsers and filters may still let it through.
The domain was registered on 2026-05-20 through Fewmoretaps OU d/b/a Trustname.com. That was roughly three and a half months before we detected it, which leaves room for the site to be built out and promoted before drawing attention. It sits behind Cloudflare's network, geolocated to Canada, so the address visitors see belongs to the proxy rather than the server actually hosting the page.
If you signed in on indexflower.com, change that password wherever you reuse it and turn on two-factor authentication. If you connected Google, analytics or advertising accounts, remove the third-party access from those accounts' security settings and check for unfamiliar users or campaigns. If you paid by card, ask your bank to dispute the charge and watch for further debits. Defenders should block the domain at DNS and proxy level and search logs for any staff who visited or submitted forms there.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/AvukatAhmetYilmazStored page referenceIoC extraction recorded 2026-09-05 04:00:15 UTC
Reputasi Edge-IP tidak dikaitkan dengan domain ini.
elias.ns.cloudflare.comtessa.ns.cloudflare.comLocation describes the IP network.
a7432120ac7dc6e9e6971b11e352062a7d2cf7eaa01b7f20040733a9fbee0169Saved 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 indexflower.com · checked Sep 5, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
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
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
5→Observation retained
Dapat dijangkau
5/92 engine detections
View source4 community references
View sourceNo threat flag
View sourceindexflower.com
View sourcePage captured
View source52 domain serupa tersimpan
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
indexflower.com
Listed 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 ↗
indexflower.com)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.