セキュリティレポートへ移動
ドメインのセキュリティと脅威インテリジェンス
honeylink.cc favicon

honeylink.cc

“honeylink.cc — агрегатор ресурсов”

レジストラ
Cloudflare
Resolved IP
104.21.24.153
Registered
2026年6月26日
PhishDestroy assessment クリティカル
可用性 最後に確認されたアクティブな状態 最新の保存された到達可能性の観測 観測された · HTTP probe
VirusTotal 検出数: 4/92 Spamhaus DBL: DBL_SPAM 自動ブランドラベル:Kraken
2026年10月19日 CDN
API
このドメインは悪意のあるものとして報告されています
検出を報告するセキュリティ エンジン: 4。 細心の注意を払ってください — 資格情報や個人情報を入力しないでください。
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
レポート概要

Krakenなりすまし: honeylink.cc — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 4/92 (alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, Webroot); Spamhaus…

元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。

Source evidenceVirusTotal 4 / 92 6 sources

Spamhaus DBL

DBL_SPAM

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

クリティカル
VirusTotal
4 / 92
Page captures
3

PhishDestroy threat report

Overview

The domain honeylink.cc appeared on the PhishDestroy blocklist on 2026-10-19. No clear brand or service is impersonated, but the timing and detection pattern suggest it is aimed at cryptocurrency users. PhishDestroy’s first observation records the site status as unknown as of the same date. The domain is therefore treated as a potential phishing or wallet‑draining portal.

How the scam works

Typical operations for a site of this type involve presenting a fake login or wallet‑connection page that asks visitors for private keys, seed phrases, or to approve blockchain transactions. When a victim supplies credentials or authorizes a transaction, the attacker can move the funds to an address they control. The loss is usually the entire balance of the compromised wallet, as the attacker can instantly drain it once approval is granted.

Evidence

VirusTotal scanned honeylink.cc on 2026-10-19 and returned four positive detections out of ninety‑two engines. The flagging vendors are alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet and Webroot, all of which label the site as malicious. The domain is also listed on the PhishDestroy blocklist. No additional detections from Google Safe Browsing, urlscan.io, or Spamhaus are recorded at this time.

Infrastructure

The domain was registered on 2026-06-26 through Cloudflare, Inc., giving it roughly four months of existence before being flagged. Hosting resolves to the IP address 172.67.219.72, which belongs to Cloudflare’s global content‑delivery network, indicating the operators are using a reputable CDN to mask the origin server. No specific TLS issuer information is available beyond the standard Cloudflare certificate.

What to do

Anyone who entered wallet credentials, private keys, or approved transactions on honeylink.cc should immediately change all related passwords, enable strong two‑factor authentication, and revoke any blockchain approvals granted to unknown addresses. Monitor wallet activity for unauthorized transfers and consider moving remaining funds to a new, secure wallet. Security teams should block honeylink.cc at the DNS and proxy layers, add the domain to internal blocklists, and watch for newly registered domains using the same registrar or hosting provider that exhibit similar malicious patterns.

Extracted from stored page analysis

Observed indicators

0 wallet · 12 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

Telegram
https://t.me/+6IUKIYdACOE1OTBkStored page reference
Telegram
https://t.me/+sBEeeNX_0pQzNDE6Stored page reference
Telegram
https://t.me/MmoparanoidStored page reference
Telegram
https://t.me/SlimeChange_botStored page reference
Telegram
https://t.me/ashoo_comStored page reference
Telegram
https://t.me/black156botStored page reference
Telegram
https://t.me/honeylink1_botStored page reference
Telegram
https://t.me/honeylinksupStored page reference
Telegram
https://t.me/nv_6_botStored page reference
Telegram
https://t.me/omglinkStored page reference
Telegram
https://t.me/rocket_btc_botStored page reference
Telegram
https://t.me/zeleniymir420botStored page reference

IoC extraction recorded 2026-10-20 04:00:09 UTC

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

保存済みキャプチャ · 3 captures

Domain details

ドメイン
URLScan verdict 分析完了 score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP の評判はこのドメインに起因しません。
レジストラ Cloudflare US(US)
不正利用連絡先["registrar-abuse@cloudflare.com"]
ICANNレジストリICANN Lookup (RDAP) →
登録情報作成日 2026年6月26日 (116d) — Expires 2027年6月26日
HTTPステータス200
技術詳細Provenance & timestamps
初確認2026年10月19日
DOM Analysisanalyzed 2026年10月19日score 71/1002 brand signals
IoC Extractionscanned 2026年10月20日0 wallet · 12 Telegram IoCs
Submitted URLhttps://honeylink.cc/
Favicon Hash
Observed page title
honeylink.cc — агрегатор ресурсов
Automated brand references
Kraken Telegram
TLS証明書
発行者 Google Trust Services / WE1 · stored validity ends in 32 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.24.153
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP の評判はこのドメインに起因しません。

ネームサーバー 2

  • hunts.ns.cloudflare.com
  • ophelia.ns.cloudflare.com

Location describes the IP network.

TLS証明書

Issuer
Google Trust Services / WE1
Valid from
2026-08-24 12:46:58
Valid until
2026-11-22 13:45:28
Validity
Within stored validity dates
Collection time
2026-10-19 13:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprintc63459fd317fd3d544d7aacb6d91ae8f33fcaeebc1fe7046e75f2ef57b99da4f

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-19 23:02:59 UTC

Primary outcome コンテンツ公開中 reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation コンテンツ公開中 Ordinary HTTP content served 90% 2026-10-19 23:02:59 UTC
RDAP registration 不明
Observed timeline last reachable: 2026-10-19 23:02:59 UTC last content: 2026-10-19 23:02:59 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.
使用技術 · 5 identified
Detected via Cloudflare Radar · Wappalyzer engine
このドメインを報告する 証拠を提出し、他の人を守る手助けをしましょう

VirusTotalによる分析

4 / 92 セキュリティ ベンダーがこのドメインにフラグを立てました
View on VT
Last analyzed
alphaMountain.ai
Forcepoint ThreatSeeker
Fortinet
Webroot

アーカイブ済み証拠

Wayback Machine Snapshot
過去のスナップショットは証拠のレビューに利用可能です
View Archive
サイトパフォーマンス分析

Google PageSpeed Insights — mobile performance audit of honeylink.cc · checked Oct 19, 2026

73
Needs Work
Performance
FCP
1.68s
First Contentful Paint
LCP
2.04s
Largest Contentful Paint
CLS
0.627
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
4.17s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: https://honeylink.cc/
honeylink.cc — агрегатор ресурсов
Независимый агрегатор актуальных ссылок. Найди рабочие адреса маркетплейсов, обменников и других ресурсов.
対応
HTTP 200
HTML body
146.4 KB
Compressed
14.3 KB
Links
37 internal · 57 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
X-Powered-By: Express
Cache-Control: public, max-age=0, s-maxage=60, stale-while-revalidate=120
CF-Cache-Status: EXPIRED
Content-Encoding: gzip
Server: cloudflare
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: 7f456bb9bdd04b45c80aef0f2bb64c7d33e86df720a1a714d3ae73f827b94dac
Open Graph title: honeylink.cc — агрегатор ресурсов
Open Graph description: Независимый агрегатор актуальных ссылок. Найди рабочие адреса маркетплейсов, обменников и других ресурсов.
Saved response-header values · 13
alt-svc
h3=":443"; ma=86400
Cache-Control
public, max-age=0, s-maxage=60, stale-while-revalidate=120
cf-cache-status
EXPIRED
CF-RAY
a4cfc505b9f5141d-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Mon, 19 Oct 2026 12:26:10 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=PL0v5ibR1cQiB8HP8ieLvIvTxGjeDITnTgG44CkJiXyN0G4WTiXVH%2BBuIZ2NiR9vNWwQ5GZf1L%2BXHoSZvUa8JmxRYBsXQt%2Be7XSKsQBrSPNLpwzdyFQ3wNJgZWvQZhk%3D"}]}
Server
cloudflare
Transfer-Encoding
chunked
X-Powered-By
Express

Values retained by the collector; long values may be shortened during collection.

Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history2

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    不明→live_content

    content_served

  2. Availability monitor · First collection record

    到達可能

Recorded activity

4 entries
  1. URLScan

    Page captured

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    4/92 engine detections

    View source
  4. Added to PhishDestroy

    honeylink.cc

    View source

類似ドメイン

保存された類似ドメイン:114 件

すべて表示(88)
kkraken.com repetition kr2aken.com insertion kraaken.com repetition kraekn.com transposition kraen.com omission kraiken.com insertion krak3n.com replacement krake.com omission krakeb.com replacement krakeen.com repetition krakeh.com replacement krakencom.com various krakewn.com insertion krakien.com insertion krakin.com vowel-swap krakjen.com insertion krakken.com repetition krakn.com omission krakne.com transposition krakon.com vowel-swap krakren.com insertion krakrn.com replacement krakwen.com insertion krakwn.com replacement kralen.com replacement kramen.com replacement kreaken.com insertion krkaen.com transposition krken.com omission kroken.com vowel-swap krraken.com repetition krsken.com replacement kruken.com vowel-swap kryken.com replacement ktaken.com replacement lkraken.com insertion lraken.com replacement mkraken.com insertion mraken.com replacement okraken.com insertion raken.com omission rkaken.com transposition craken.com bitsquatting jraken.com bitsquatting k-raken.com hyphenation k2aken.com bitsquatting kbaken.com bitsquatting kpaken.com bitsquatting kra-ken.com hyphenation kracen.com bitsquatting krajen.com bitsquatting krak-en.com hyphenation krakan.com bitsquatting krakel.com bitsquatting kraken1.com addition kraken2.com addition kraken3.com addition kraken4.com addition kraken5.com addition kraken6.com addition kraken7.com addition kraken8.com addition kraken9.com addition krakena.com addition krakenc.com addition krakene.com addition krakenf.com addition krakeng.com addition krakenh.com addition krakeni.com addition krakenk.com addition krakenl.com addition krakenn.com addition krakeno.com addition krakenr.com addition krakens.com addition krakent.com addition krakenv.com addition krakenx.com addition krakeny.com addition krakenz.com addition kraker.com homoglyph krakgn.com bitsquatting krakmn.com bitsquatting krakun.com bitsquatting kreken.com bitsquatting kriken.com bitsquatting kvaken.com bitsquatting

114 件中 100 件を表示

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

honeylink.cc

証拠および外部報告書

詳細な分析
Help & reporting

このサイトによって何か影響を受けましたか?

3 evidence signal groups linked 0 stored notification records 最後に確認されたアクティブな状態

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.

アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。

Official reporting routes

復旧を装った詐欺に注意! 犯罪者は、捜査員、弁護士、または回収業者を装い、被害者に再び連絡を取る可能性があります。 前払い料金を支払ったり、資格情報を共有したりしないでください。 回復詐欺について詳しくはこちら →

お住まいの地域の当局へ報告してください

サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。

97か国のディレクトリ

Template-based draft · optional AI wording assistance requires separate consent

AI 支援ドラフト — インシデントの詳細は AI プロバイダーによって処理されます · 自分で確認して送信する
After a phishing incident

被害者への推奨事項とアドバイス

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.

  • すべてのパスワードを変更する — メール、Exchangeアカウントなど、同じパスワードを使用しているものすべて
  • 2段階認証を有効にする 認証アプリ(SMSではない)を使用する。SMSによる復旧機能を無効にする
  • カードの凍結 フィッシングサイトに銀行口座情報を入力してしまった場合

レポート作成のために、どのような情報を収集すべきでしょうか?

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.
  • 正確な日時 — 各取引および詐欺師との最初の接触について
  • スクリーンショット — 詐欺サイト、チャットメッセージ、メール、ウォレットでの取引、ソーシャルメディア
  • すべてのURLおよびドメイン 詐欺師が使用した(以下を含む) honeylink.cc)
  • コミュニケーション — 詐欺師が使用したメール、テキストメッセージ、電話番号、ユーザー名

たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。

この詐欺はどこに通報すればいいですか?

  • FBI IC3 — インターネット犯罪通報センター(米国連邦政府の通報窓口)
  • ユーロポール — 欧州におけるサイバー犯罪の報告(EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • 地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される

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?

  • 偽のウェブサイト — 正規サイトのドメインをわずかに変更した、ピクセル単位で完璧に再現されたクローンサイト
  • pig butchering — TelegramやWhatsApp、出会い系アプリを通じて数週間にわたって信頼関係を築き、その後、金銭をだまし取られる
  • 詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AIを利用した詐欺 — ディープフェイク、自動化されたフィッシング、AI生成サイトにより、詐欺の発見が難しくなっている

今後、どうすれば身を守ることができるでしょうか?

  • 公式サイトをブックマークする — メール、DM、広告に含まれるリンクは絶対にクリックしないでください
  • ドメインの確認 — 確認する PhishDestroy 操作を行う前に、HTTPS、スペル、ドメインの登録期間を確認してください。
  • 「良すぎて怪しい」=詐欺 — 確実なリターン、有名人の推薦、差し迫った締め切り

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

最新情報を入手し、安全を確保しましょう

リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください

リアルタイム脅威情報フィード この掲載情報について異議を申し立てる
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

このレポートを埋め込む

この脅威情報を、ご自身のウェブサイトやブログで共有してください

embed.html
<iframe
  src="https://phishdestroy.io/ja/embed/domain/honeylink.cc"
  title="PhishDestroy threat report for honeylink.cc"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>