VirusTotal
2 / 91 engine detections
보고서 열기“Un instant…”
jup.humidifi.network — 클로킹됨 · 접근 가능 (HTTP 403). 사기 유형: Impersonation. 증거 요약: VirusTotal 2/91 (Chong Lua Dao, Gridinsoft); cloaking observed; PhishDestroy score 86/100. 등록기관: Cloudflare.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
2 / 91 engine detections
보고서 열기no community references
보고서 열기provider verdict: clean
보고서 열기No threat flag
보고서 열기No malicious flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
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.
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.
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
Location describes the IP network.
01d3a1ec403a37940bf4ec67accb57431cb00547b7d19826d3abdf9e929c3424humidifi.networkSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
status_split · cloudflare_challenge: raw=cf_challenge; http=403; via=https_proxy; server=cloudflare
jup.humidifi.network
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
알 수 없음→protected
cloudflare_challenge · Cloudflare · challenge
이용 불가→접속 가능
https://radar.cloudflare.com/scan/51a09a65-8b2f-4911-a46b-717069c3ac92
https://radar.cloudflare.com/scan/77cebee3-868b-4e74-a645-1b7796108f45
접속 가능→이용 불가
No threat flag
View source2/91 engine detections
View sourcePage captured
View sourcejup.humidifi.network
View source커뮤니티 구성원 1명이 신고 · 최초 확인 2025년 12월 3일
Listed domains receive at least one abuse report; this entry has no retained notification history.
계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
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 ↗
jup.humidifi.network)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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
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.