Analysis indicates that the domain jupi.humidifi.network is presently active and categorized as a generic phishing operation. The site returns an HTTP 403 status and presents the page title "Just a moment...", suggesting that the content is being gated or protected by a challenge mechanism. Infrastructure profiling shows the domain resolves to IP address 172.67.132.209, which is part of a large content delivery network located in the United States and associated with ASN 13335. The TLS certificate is issued by a major certificate authority and uses a modern encryption suite. Reputation data includes a Gridinsoft trust score of 0 out of 100, placement on three security blocklists, and detection by two of ninety‑five scanners on a public multi‑engine service. The domain is also listed by at least three independent anti‑phishing listings. No additional forensic detail about the actual phishing payload, target brand, or page layout is available beyond the generic title. Given the confirmed active status, low trust rating, and multiple blocklist entries, defenders should treat the domain as malicious, enforce network‑level blocking, consider DNS sinkholing, and monitor for any related activity originating from the same IP range or certificate fingerprint. Ongoing observation is advised to capture any future changes to the site content or hosting configuration.
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.
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-13 02:00:46 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 02:00:46 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.
技术 · 3 identified
Cloudflare Browser Insights
AnalyticsRUM
Performance monitoring tool that measures website speed from real users.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
(US)
