VirusTotal
5 / 92
“krakendarknet.site”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@reg.ru.
The latest stored availability evidence still shows the domain reachable; 13 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
krakendarknet.site — 最後に確認されたアクティブな状態 (HTTP 200). ブランドの偽装: Kraken; 詐欺タイプ: Impersonation. 証拠の概要: VirusTotal 5/92 (alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft, LevelBlue, SOCRadar); PhishDestroy score 88/100. レジストラ: Registrar of Domain Na….
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
krakendarknet.site returned HTTP status 200 on 2026-10-01, according to the recorded HTTP check. The domain was first observed on 2026-09-28, and its registration date is listed as 2025-12-31.
The HTTP check on 2026-10-01 recorded status 200 for krakendarknet.site. The domain was first observed on 2026-09-28, while its registration date is recorded as 2025-12-31. VirusTotal, checked on 2026-09-29, reported 3 detections across 91 scanners. OTX, checked on 2026-10-01, showed 4 pulses. The publisher-owned PhishDestroy catalogue listed the domain, and the PageSpeed check on 2026-09-28 returned a performance score of 67.
The HTTP and OTX checks share the 2026-10-01 date, so those two observations describe the same day, while the VirusTotal check on 2026-09-29 and the PageSpeed check on 2026-09-28 precede them. Because the first observation on 2026-09-28 is earlier than the registration date of 2025-12-31, the recorded timeline spans several months. Comparing these dated sources shows how the recorded picture can shift between checks rather than reflecting a single moment.
Reviewers should retain the dated records for krakendarknet.site, including the HTTP, VirusTotal, OTX and PageSpeed observations, so later checks can be compared against them. Any subsequent HTTP or OTX check should be dated and compared with the earlier entries rather than treated as a replacement. During review, avoid submitting sensitive information to the domain, since the recorded HTTP status alone does not establish what the site currently serves.
このホストに関するクローラーとブラウザの観測データの蓄積に加え、ケイタロ式トラフィック分散システム向けのリアルタイムフィンガープリントチェック。
openrestyスキャナーに関する注記: alive_content: raw=ok; http=200; via=https_proxy; server=openresty
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.
ns1.reg.runs2.reg.ruLocation describes the IP network.
309e705fc996693bfc0643d536d2bba1454dc0f09428afac6e2089b4ebe19c8ewww.krakendarknet.siteSaved 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 krakendarknet.site · checked Sep 28, 2026
95.163.244.138. 16 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
保存された類似ドメイン:114 件
114 件中 100 件を表示
PD-20260928-039BF8 Recipient: abuse@reg.ru Registrar: REG.RU (Russia) Policy Violations: Abuse policy + ICANN contractual obligations; phishing classified as bad-faith use in UDRP; domains may be suspended/removed Applicable Laws: Criminal Code RF Art.159 (fraud), Art.272 (illegal access), Art.273 (malware creation), Art.274.1 (critical infrastructure interference)
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
Template-based draft · optional AI wording assistance requires separate consent
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください