ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
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; 12 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.
On 2026-10-01 krakendarknet.su returned HTTP status 200 in a recorded HTTP check, and the domain was first observed on 2026-09-29. A PageSpeed check on 2026-09-29 recorded a performance score of 96 for the domain.
Recorded Evidence
VirusTotal recorded 5 detections across 91 scanners on 2026-09-29. OTX listed 4 pulses on 2026-10-01, and the PhishDestroy internal catalogue carried a listing on that date. The registrar was recorded as REGRU-SU, and the SSL issuer was recorded as Let's Encrypt / YR2.
Interpretation
The VirusTotal detections and OTX pulses are distinct source observations with different scopes, so they cannot be merged into one conclusion. The HTTP 200 response documents only the recorded status on its check date and does not describe all content served by the domain. The PageSpeed score reflects a separate measurement on its own date.
Recommended Actions
Preserve the VirusTotal and OTX records for krakendarknet.su so future scans can be compared against them. Compare the PhishDestroy catalogue entry with the HTTP response record in separate reviews. Keep the PageSpeed result alongside the other source records as a baseline for later checks.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='krakendarknet.su', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
DOM Analysisanalyzed 2026年10月9日score 88/1001 brand signal
Submitted URLhttps://krakendarknet.su/
Favicon Hash
ケース ID
ページタイトル
krakendarknet.su
Impersonates
Kraken
TLS証明書
Certificate hostname mismatch·
発行者 Let's Encrypt / YR2· stored validity ends in 60 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
95.163.244.138
Network ASN
AS197695
Organization
"Domain names registrar REG.RU", Ltd
Observed location
Moscow, RU
Server header
openresty
ネームサーバー 2
ns1.reg.ru
ns2.reg.ru
Location describes the IP network.
TLS証明書
Issuer
Let's Encrypt / YR2
Valid from
2026-09-11 21:59:23
Valid until
2026-12-10 21:59:22
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-29 01:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint36799fefe25e2b35783ebb031539693c4990b65a8216a6d853bcac5b524e27edCertificate names · 1 SANs
www.krakendarknet.su
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 10:31:12 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-07 02:49:39 UTClast content: 2026-10-07 02:49:39 UTCcurrent episode first observed: 2026-10-08 20:20:32 UTCobserved RIP window: 2026-10-07 02:49:39 UTC → 2026-10-08 20:20:32 UTC · 41.51hmidpoint estimate ≈ 2026-10-07 23:35:05 UTC · precision medium · basis bounded
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.
使用技術 · 3 identified
N
Nginx
Web serversReverse proxies
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Fortinet
LevelBlue
SOCRadar
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of krakendarknet.su· checked Sep 29, 2026
96
Good
Performance
FCP
1.24s
First Contentful Paint
LCP
2.31s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
124ms
Total Blocking Time
SI
3.59s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
VirusTotal Detections Update2026-09-29 06:51:43 UTC
VirusTotal scanner detections updated from 4 to 5. Added scanner alerts: CRDF.
VirusTotal Detections Update2026-09-29 03:06:45 UTC
VirusTotal scanner detections updated from 5 to 4. Resolved alerts: CRDF.
VirusTotal Detections Update2026-09-29 02:35:01 UTC
VirusTotal scanner detections updated from 4 to 5. Added scanner alerts: CRDF.
VirusTotal Detections Update2026-09-29 02:04:40 UTC
VirusTotal scanner detections updated from 0 to 4. Added scanner alerts: Forcepoint ThreatSeeker, Fortinet, SOCRadar, alphaMountain.ai.
Threat First Observed2026-09-28 22:27:46 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 95.163.244.138.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
