The domain jup.humidifi.network has been identified as a high-risk phishing domain. As of July 12, 2026, the domain remains active and is flagged by one out of 95 security vendors on VirusTotal, indicating a low but significant level of detection. The Gridinsoft trust score for this domain is 0 out of 100, which suggests a complete lack of trustworthiness. The domain is currently blocked by PhishDestroy, an additional indicator of its malicious nature. The domain is registered through Cloudflare, Inc., and resolves to the IP address 172.67.132.209, which is located in the United States and is part of the Cloudflare, Inc. network (AS13335). The SSL certificate for the domain is issued by Google Trust Services, using the WE1 certificate authority. This suggests that while the domain may appear to have a legitimate SSL certificate, the underlying infrastructure and trust score indicate otherwise. The HTTP status code for the domain is 403, which typically means that the server understood the request but refuses to authorize it. This could be due to the domain being blocked or the server being configured to deny access to certain clients, which is a common tactic used by malicious actors to evade detection. Defenders should be cautious and monitor this domain closely, as the active status and low trust score indicate a potential ongoing threat. It is recommended to block access to this domain at the network level and to educate users about the risks associated with clicking on links from unknown sources. Since the exact content of the domain has not been analyzed, further investigation is necessary to determine the specific nature of the phishing attempt and to identify any potential targets or payloads. Defenders should also consider conducting a deeper analysis of the domain's DNS records, WHOIS information, and associated IP addresses to uncover additional indicators of compromise and to understand the broader threat landscape.
For the registrable domain humidifi.network behind this subdomain, 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.
Accountability draft
Tidak ada yang dikirim secara otomatis.
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
172.67.132.209
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare
Reputasi Edge-IP tidak dikaitkan dengan domain ini.
Location describes the IP network.
Sertifikat TLS
Issuer
Google Trust Services / WE1
Valid from
2026-01-31 06:19:41
Valid until
2026-05-01 07:18:12
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-03-11 19:31:24 UTC
Collection source
PhishDestroy collector
Certificate fingerprint01d3a1ec403a37940bf4ec67accb57431cb00547b7d19826d3abdf9e929c3424Certificate names · 1 SANs
humidifi.network
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeReachable but protectedreason: Cloudflare Challenge85% confidence
AttributionCloudflaremechanism: Challengesource: Current Http Probe
Evidence layersAvailability: Reachable but protectedContent: UnknownDNS: ResolvedRegistration: Unknown
Latest HTTP observationReachable but protectedCloudflare ChallengeCloudflareChallenge85%2026-10-21 01:31:38 UTC
RDAP registrationTidak diketahui
Observed timelinelast reachable: 2026-10-21 01:31:38 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
Cloudflare
CDN
Web infrastructure and security company providing CDN, DDoS mitigation, and DNS services.
Hubungan yang disimpan dikelompokkan berdasarkan atribut pencocokan tepat. Penyedia atau registrar bersama saja tidak membuktikan kepemilikan bersama.
Peta infrastruktur · jup.humidifi.network
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 cocok8
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.
4 evidence signal groups linked0 stored notification recordsTerselubung · dapat dijangkau
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 jup.humidifi.network)
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.
(US)
