VirusTotal
6 / 91 engine detections
レポートを開く“Home – Huddle01's Documentation”
フィッシング: huddle01.download — 未検証. 証拠の概要: VirusTotal 6/91 (alphaMountain.ai, Chong Lua Dao, CRDF, Fortinet, Gridinsoft); Spamhaus DBL_PHISH; PhishDestroy score…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 91 engine detections
レポートを開くDBL_PHISH
checked — no detections recorded
レポートを開く24 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くPage capture
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
Analysis on huddle01.download indicates an active brand‑impersonation campaign targeting Discord users. The domain was registered on 21 February 2026 through NiceNIC International Group Co., Limited and resolves to the Cloudflare‑hosted address 66.33.60.67, which is announced as part of AS13335 (Cloudflare, Inc.) and located in the United States. The site is served behind Cloudflare, using HTTP/3 and presents a valid SSL certificate issued by Google Trust Services under the WE1 root, suggesting the TLS handshake is not being abused. However, the HTTP response code is 521, indicating that the origin server is refusing connections, a pattern often observed in temporary phishing infrastructure that relies on Cloudflare’s edge caching.
Reputation checks show a Gridinsoft trust score of 0 / 100 and three independent blocklists have already listed the domain. VirusTotal records show that 7 of 93 scanning engines have flagged the domain, and it appears in a single AlienVault OTX pulse, confirming that threat‑intel communities have observed malicious activity. The domain is also specifically blocked by PhishDestroy, MetaMask, and SEAL, reinforcing the classification as a brand‑impersonation site. The page title returned by the server is “Home – Huddle01’s Documentation”, which does not reference Discord and suggests the content may be a generic landing page used to host malicious payloads or credential‑harvesting forms, although the exact page content has not been publicly disclosed.
The primary uncertainty lies in the current state of the backend service, given the 521 status, and whether the site is actively serving phishing pages or merely staging infrastructure. Defenders should add 66.33.60.67 and huddle01.download to URL filtering and DNS block lists, monitor for any outbound connections to that IP, and enforce multi‑factor authentication for Discord accounts to mitigate credential compromise.
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.
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 の評判はこのドメインに起因しません。
arnold.ns.cloudflare.comLocation describes the IP network.
82fce5a50f8044b93abce24e73f699189a3ab1769d92dabe3f07785e2686dc7dSaved 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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='huddle01.download', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
huddle01.download
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
到達可能→利用不可
https://radar.cloudflare.com/scan/ad41b916-5b72-472a-aa35-a25e5777bcab
https://radar.cloudflare.com/scan/838d4d44-907d-44a5-b075-3fc93b354912
到達可能→利用不可
到達可能→利用不可
24 community references
View source6/91 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcehuddle01.download
View sourcePD-20260130-6F1D93
保存された類似ドメイン:118 件
118 件中 100 件を表示
コミュニティの 1 人が報告・初回確認 2026年1月30日
PD-20260130-6F1D93 Recipient: abuse@nicenic.net Registrar: NICENIC International Group Co., Limited (Hong Kong (China)) Policy Violations: “Services may be used only for lawful purposes… fraud, abuse and illegal activity prohibited. Violations may result in immediate suspension.” + dedicated abuse handling and takedown Applicable Laws: Crimes Ordinance Cap.200 (Fraud), Theft Ordinance Cap.210 §16A (fraud by deception), Personal Data (Privacy) Ordinance Cap.486
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
huddle01.download)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.