VirusTotal
2 / 91 engine detections
レポートを開く“Contact Support”
Krakenなりすまし: kraken.com.support.bc1q8zca56ds9j9zwxvln3e96p9em55h62048q04py.sevvel.properties — コンテンツが利用できません. 証拠の概要: VirusTotal 2/91 (ChainPatrol, Fortinet)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
2 / 91 engine detections
レポートを開くchecked — no detections recorded
レポートを開くno community references
レポートを開く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
Analysis of the domain kraken.com.support.bc1q8zca56ds9j9zwxvln3e96p9em55h62048q04py.sevvel.properties indicates an active generic phishing infrastructure. The domain resolves to the IPv4 address 162.215.240.27; no authoritative nameserver records are returned, which hampers attribution of the hosting environment. VirusTotal reports that two out of ninety‑one scanning engines have flagged the domain, providing limited but corroborating evidence of malicious use. The threat is classified as high risk and remains active as of the report date. Concrete evidence is limited to the IP resolution and the modest detection count; no additional intelligence such as malware samples, phishing kits, or associated command‑and‑control infrastructure has been observed. Consequently, uncertainty remains regarding the full scope of the campaign, the hosting provider, and any potential reuse of the same IP for other malicious actors. Defenders should block DNS resolution to the domain and the associated IP address at network perimeter devices, monitor outbound traffic for connections to 162.215.240.27, and incorporate the domain into threat‑intel feeds. Continuous re‑evaluation is recommended to capture any changes in detection status or the emergence of further indicators.
Last checked
For the registrable domain sevvel.properties 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.
ns2.bh-11.webhostbox.netLocation describes the IP network.
e340355bf1cf37eafbec0fcd3a9e28dacd75b400dc324d319c5c73f670100ebfkraken.com.support.bc1qe0w4evp7rd9vx0h0tgym68z6njuqrhq3nlajz4.sevvel.propertieswww.kraken.com.support.bc1q8zca56ds9j9zwxvln3e96p9em55h62048q04py.sevvel.propertieswww.kraken.com.support.bc1qe0w4evp7rd9vx0h0tgym68z6njuqrhq3nlajz4.sevvel.propertiesSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.kraken.com.support.bc1q8zca56ds9j9zwxvln3e96p9em55h62048q04py.sevvel.propertiesDomain recordThe original observation time is not recorded for these hostnames.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
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
到達可能→利用不可
Page captured
View source2/91 engine detections
View sourceNo threat flag
View sourcePD-20260715-7B8C42
kraken.com.support.bc1q8zca56ds9j9zwxvln3e96p9em55h62048q04py.sevvel.properties
View source保存された類似ドメイン:114 件
114 件中 100 件を表示
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
kraken.com.support.bc1q8zca56ds9j9zwxvln3e96p9em55h62048q04py.sevvel.properties
PD-20260715-7B8C42 Recipient: abuse@publicdomainregistry.com Registrar: PublicDomainRegistry (PDR Ltd.) (India) Policy Violations: Explicit policy to immediately suspend domains used for phishing, 419 scams, identity fraud, malware distribution without prior notice Applicable Laws: IT Act 2000 §§66C–66D (identity theft, cheating by personation), Indian Penal Code §420 / Bharatiya Nyaya Sanhita §318 (fraud)
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
kraken.com.support.bc1q8zca56ds9j9zwxvln3e96p9em55h62048q04py.sevvel.properties)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.