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.
Extracted from stored page analysis
Observed indicators
0 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
DOM Analysisanalyzed 2026年10月20日score 10/1003 brand signals
IoC Extractionscanned 2026年7月29日0 wallet · 1 Telegram IoC
Submitted URLhttp://mail.kraken-gur.support/
Favicon Hash
ICANN OVERSIGHTRegistration: kraken-gur.support
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
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.
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 fingerprinta5c255070ebd48e3652f3a82a1d5f9fcb7d6a49d844723f3898fe1a7f5987f48Certificate names · 1 SANs
kraken-gur.support
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-19 22:31:04 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-19 22:35:34 UTClast content: 2026-10-19 22:31:04 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
P
PHP
Programming languages
Server-side scripting language designed for web development.
B
Bootstrap
UI frameworks
Popular CSS framework for responsive, mobile-first web development.
L
LiteSpeed
Web servers
High-performance web server compatible with Apache configurations.
J
jQuery
JavaScript libraries
Fast, small JavaScript library simplifying HTML manipulation, event handling, and Ajax.
H
HTTP/3
Miscellaneous
Third major version of HTTP protocol, built on QUIC for faster, more reliable connections.
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 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（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.
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?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(CZ)
