Analysis of the domain app.tubors.finance shows it was registered on February 21, 2026. The domain is classified as a generic phishing infrastructure and carries an elevated risk rating. VirusTotal scans indicate that six of ninety‑three security vendors flagged the domain as malicious, providing independent corroboration of its abusive nature. Current connectivity checks confirm that the domain is taken offline, and the PhishDestroy service has explicitly blocked it.
Additionally, the domain appears on one external security blocklist, reinforcing the consensus that it should be treated as hostile. No public information is available regarding the hosting provider, IP address, SSL certificate, or HTTP response details beyond the offline status, and no page title or brand attribution has been disclosed. The limited observable data therefore centers on registration timing, vendor detections, and blocklist presence. Defenders should ensure that app.tubors.finance is added to internal deny lists across DNS resolvers, firewalls, and web filters.
Continuous monitoring of DNS query logs for this FQDN is advised to detect any attempts at re‑activation. Threat hunters should also watch for related domains created in the same period that exhibit similar detection patterns, as the actor may reuse infrastructure. Given the elevated risk level and existing vendor flags, proactive blocking and alerting are recommended to prevent potential phishing campaigns that could target users through this domain.
Registration (base domain)tubors.finance · Dibuat 21/02/2026 (241d)
Waktu hingga pertama kali tidak tersedia39 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.
Primary outcomeDNS tidak aktifreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationTidak diketahuiProbe Inconclusive20%2026-10-19 01:16:00 UTC
RDAP registrationTidak diketahui
Observed timelinelast reachable: 2026-09-21 01:41:04 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-21 01:41:04 UTC → 2026-09-30 16:14:55 UTC · 230.56hmidpoint estimate ≈ 2026-09-25 20:57:59 UTC · precision low · 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.
Last analyzed Previous stored snapshot: 15 detections
ChainPatrol
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
Sophos
VIPRE
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
230.56
Estimate basis
Bounded by observations
Estimate precision
Low
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.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='app.tubors.finance', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
app.tubors.finance
Hasil tersimpan
Tidak dapat dijangkau
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
3 evidence signal groups linked0 stored notification recordsKonten 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.
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 app.tubors.finance)
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)
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
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.
