VirusTotal
3 / 91 engine detections
レポートを開く“НАЦІОНАЛЬНА БЛАГОДІЙНА ЛОТЕРЕЯ”
Krakenなりすまし: mail.kraken-gur.support — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 3/91 (ChainPatrol, Forcepoint ThreatSeeker, Gridinsoft); PhishDestroy…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
3 / 91 engine detections
レポートを開く2/14
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 mail.kraken-gur.support is currently active and classified as a high‑risk brand‑impersonation infrastructure targeting Kraken users. Registration data shows the domain was created on September 24, 2025 through Hosting Concepts B.V. d/b/a Registrar.eu, and it resolves to the IPv4 address 45.94.159.104, which is geolocated to Ukraine and assigned to AS56851 (PE Skurykhin Mukola Volodumurovuch). The authoritative nameservers are dns1.hostiq.ua and dns2.hostiq.ua, and the domain publishes an MX record (priority 0) pointing to kraken-gur.support, suggesting an attempt to receive email from potential victims. A TLS certificate issued by Let’s Encrypt (R12) is present, and the web server returns HTTP 200 responses, indicating a live site.
The page title returned by the server is "НАЦІОНАЛЬНА БЛАГОДІЙНА ЛОТЕРЕЯ", which does not reference Kraken but further demonstrates the site is being used for a crypto‑related scam. Technology fingerprints include PHP, Bootstrap, LiteSpeed, jQuery and HTTP/3, confirming a modern web stack. Reputation checks show a Gridinsoft trust score of 0 / 100 and two of ninety‑five VirusTotal scanners flag the domain, while it appears on a single security blocklist and is already blocked by PhishDestroy. These indicators collectively point to an active phishing campaign that masquerades as Kraken communications to lure victims into a cryptocurrency scam.
Uncertainty remains around the exact phishing workflow, such as whether credential harvesting or direct fund transfer pages are hosted, because no visual analysis of the landing page is available. Defenders should add the domain and its associated IP address to firewall and DNS blocklists, monitor for outbound connections to the host, and enforce email filtering that flags any messages originating from the kraken-gur.support MX host. Continuous re‑scanning with multi‑vendor engines is advised to capture any evolving malicious payloads.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/kraken_gur_officialStored page referenceIoC extraction recorded 2026-07-29 02:40:16 UTC
For the registrable domain kraken-gur.support 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.
dns1.hostiq.uadns2.hostiq.uakraken-gur.supportpriority 0Location describes the IP network.
a5c255070ebd48e3652f3a82a1d5f9fcb7d6a49d844723f3898fe1a7f5987f48kraken-gur.supportSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of mail.kraken-gur.support · checked Mar 6, 2026
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.
alive_content: raw=ok; http=200; via=https_proxy; server=LiteSpeed
mail.kraken-gur.support
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
No threat flag
View source3/91 engine detections
View sourcePage captured
View sourcemail.kraken-gur.support
View source保存された類似ドメイン:114 件
114 件中 100 件を表示
コミュニティの 1 人が報告・初回確認 2025年12月18日
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 ↗
mail.kraken-gur.support)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.