The domain ipo.capital is active and was registered on August 23, 2024 through NameCheap, Inc. It resolves to IP address 188.114.97.3, which is part of the Cloudflare, Inc. network (AS13335) and is geolocated in the United States. TLS is provided by a Google Trust Services certificate under the WE1 root, and HTTP requests return a 200 status code with the page title “Main Page - IPO Capital”. The domain appears on one security blocklist and is flagged by PhishDestroy. VirusTotal analysis shows that 6 of 95 security vendors have marked the domain as malicious. MX records point to Google mail servers (aspmx.l.google.com, alt1.as...). The threat is classified as a crypto‑related brand impersonation, specifically targeting the brand “across”. Infrastructure analysis indicates use of a cloud‑based CDN, obscuring the true hosting environment, and no additional page content has been disclosed, leaving the exact phishing payload uncertain. Defenders should block the domain at DNS and proxy levels, monitor for connections to the associated IP, and add the domain to threat‑intel feeds. Ongoing re‑scanning is recommended to detect any changes in detection status.
DOM Analysisanalyzed 20/10/2026score 10/1003 brand signals
Submitted URLhttps://ipo.capital/
Favicon Hash
ICANN OVERSIGHT
Akreditasi dan konteks RAA
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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 22:18:53 UTC
RDAP registrationTidak diketahui
Observed timelinelast reachable: 2026-09-15 22:18:00 UTCcurrent episode first observed: 2026-10-04 22:13:35 UTCobserved RIP window: 2026-09-15 22:18:00 UTC → 2026-10-04 22:13:35 UTC · 455.93hmidpoint estimate ≈ 2026-09-25 10:15:47 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.
Teknologi · 10 identified
W
WordPress
CMSBlogs
WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. Features include a plugin architecture and a template system.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Google PageSpeed Insights — mobile performance audit of ipo.capital· checked Mar 2, 2026
52
Needs Work
Performance
FCP
2.71s
First Contentful Paint
LCP
8.13s
Largest Contentful Paint
CLS
0.22
Cumulative Layout Shift
TBT
128ms
Total Blocking Time
SI
8.04s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
455.93
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='ipo.capital', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
ipo.capital
Stored observation history14
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Hubungan yang disimpan dikelompokkan berdasarkan atribut pencocokan tepat. Penyedia atau registrar bersama saja tidak membuktikan kepemilikan bersama.
Peta infrastruktur · ipo.capital
Setiap jalur merupakan salah satu alasan mengapa sebuah domain terhubung ke host ini. Ukuran node menandai deteksi VirusTotal, sedangkan node bergaris putus-putus menunjukkan bahwa node tersebut sudah offline. Daftar lengkapnya tercantum di bawah ini.
Konten cocok4
Hash favicon yang sama atau judul halaman yang sama dengan host ini.
Laporan-laporan ini diselesaikan dengan IP edge bersama yang sama. Mereka membantu penemuan laporan tetapi tidak menyiratkan kepemilikan bersama atau server asal bersama.
Didaftarkan melalui penyedia layanan pendaftaran yang sama. Sebuah penyedia layanan pendaftaran melayani jutaan pelanggan yang tidak saling terkait, sehingga hal ini sekadar mengelompokkan laporan-laporan tersebut, bukan membuktikan adanya hubungan.
The PhishDestroy system has identified this domain as a phishing threat, flagged both by our internal parser and reported by users. We also cross-reference with public databases and other antivirus systems.
Laporan komunitas
Dilaporkan oleh 1 anggota komunitas; pertama terlihat 07/08/2025
1 report filed for ipo.capital (1 written by a person) · category: Phishing · source checked
“The PhishDestroy system has identified this domain as a phishing threat, flagged both by our internal parser and reported by users. We also cross-reference with public databases and other antivirus systems.”
— reported by Anonymous on Jun 8, 2025 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
6 evidence signal groups linked0 stored notification recordsBelum terverifikasi
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 ipo.capital)
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.
Gridinsoft Analysis
36 / 100
(US)
