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; 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 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.
Recorded Evidence
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.
Interpretation
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.
Recommended Actions
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.
DOM Analysisanalyzed 2026年10月9日score 88/1001 brand signal
Submitted URLhttps://krakendarknet.site/
Favicon Hash
案件 ID
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
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.
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 fingerprint309e705fc996693bfc0643d536d2bba1454dc0f09428afac6e2089b4ebe19c8eCertificate names · 1 SANs
www.krakendarknet.site
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-11 10:09:52 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:09:52 UTClast content: 2026-10-11 10:09:52 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.
技术 · 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.
Google PageSpeed Insights — mobile performance audit of krakendarknet.site· checked Sep 28, 2026
67
Needs Work
Performance
FCP
4.08s
First Contentful Paint
LCP
6.84s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
28ms
Total Blocking Time
SI
4.08s
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 02:08:03 UTC
VirusTotal scanner detections updated from 2 to 3. Added scanner alerts: Forcepoint ThreatSeeker, SOCRadar. Resolved alerts: LevelBlue.
VirusTotal Detections Update2026-09-28 11:45:24 UTC
VirusTotal scanner detections updated from 1 to 2. Added scanner alerts: alphaMountain.ai.
VirusTotal Detections Update2026-09-28 11:15:16 UTC
VirusTotal scanner detections updated from 2 to 1. Resolved alerts: SOCRadar.
VirusTotal Detections Update2026-09-28 06:39:40 UTC
VirusTotal scanner detections updated from 1 to 2. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-28 02:03:56 UTC
VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: LevelBlue.
Threat First Observed2026-09-28 01:33:05 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 95.163.244.138.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
16 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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
