http://krakengateway.com/HTTP 200
153 B
144 B
0 internal · 0 external
Content-Type: text/htmlAll stored response-header names (3)
Content-TypeDateContent-LengthThe sent-report ledger records the first outgoing report at . A report was sent to the recorded registrar; contact details remain in Domain Intelligence. The latest stored availability evidence still shows the domain reachable; 14 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
“Kraken Gateway”
The domain krakengateway.com was registered on 24 July 2026 through GoDaddy.com, LLC and is currently served by the authoritative nameservers ns59.domaincontrol.com and ns60.domaincontrol.com. DNS resolution points to the IPv4 address 5.78.184.96, which is the sole host observed for this indicator. The domain appears on three public security blocklists and has been explicitly blocked by the PhishDestroy, MetaMask, and SEAL filtering services. VirusTotal analysis shows that eight of ninety‑one scanned security vendors have raised detections against the domain, confirming malicious intent despite the relatively low overall count.
The intelligence source classifies the activity as generic phishing and assigns a high risk rating; the campaign remains active at the time of reporting. No public information is available regarding the web content, TLS certificate details, HTTP response codes, or the specific phishing kit employed. Consequently, the exact victim‑facing payload and any targeted brand or credential‑stealing mechanism cannot be confirmed at this stage. The lack of disclosed page title or brand association limits attribution but does not diminish the observed malicious infrastructure.
Defenders should prioritize immediate containment of krakengateway.com by adding the domain to DNS‑based deny lists and firewall rules. Network monitoring should include traffic to the IP address 5.78.184.96, and any outbound connections to that host should be logged and investigated. Given the recent registration date, threat‑intel feeds are likely to update with additional indicators; continuous re‑evaluation of blocklist status and VirusTotal scans is recommended. Organizations employing email gateways or web proxies are advised to enforce the existing blocklist entries and to consider proactive URL filtering for newly observed domains that resolve to the same hosting IP.
PD-20260728-F86C91١٠ مصادر خارجية مراقبة · لقطة محفوظة 12/08/2026
أول قيمة محفوظة: يمكن الوصول إليه
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.
حُدّدت ٣ تقنيات عالية الثقة
Google PageSpeed Insights — mobile performance audit of krakengateway.com · checked Jul 28, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://krakengateway.com/Content-Type: text/htmlContent-TypeDateContent-Lengthإذا أدخلت بيانات اعتماد الحساب أو المعلومات الشخصية أو معلومات الدفع أو قمت بتنزيل ملف من هذا النطاق، فاتخذ إجراءً فوريًا. فيما يلي موارد لمساعدتك في الإبلاغ عن الحادث وحماية نفسك.
حدد بلدك للحصول على الاتصالات الرسمية المتعلقة بالجرائم الإلكترونية أو إنشاء مسودة شكوى →.
تحليل التهديدات باستخدام قائمة الحظر المخزنة، وWHOIS، وDNS، وأدلة الفحص العامة
امسح الآنأرسل النطاقات المشبوهة إلى قاعدة بيانات التهديدات الخاصة بنا — ساهم في حماية المجتمع
إبلاغتقارير التصيد الاحتيالي الأخيرة وتغييرات التوفر الملحوظة
مراقبةراقب التهديدات في الوقت الفعلي أو اعترض على هذا الإدراج إذا كنت تعتقد أنه إنذار كاذب