Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
Stored evidence for krakenx.top: VirusTotal recorded 3 detections among 91 scanners on 2026-09-25. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for krakenx.top. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 3 detections among 91 scanners in the stored snapshot dated 2026-09-25. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-25 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
Source Context
MetaMask and SEAL are recorded as named external blocklist observations for krakenx.top in the snapshot dated 2026-09-25. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains krakenx.top as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
Reachability and Timeline
The record first observed krakenx.top on 2026-09-25. The MetaMask and SEAL blocklist snapshot is dated 2026-09-25 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-24. A URLScan reference was stored on 2026-09-25 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
Registration and Infrastructure
For krakenx.top, the registrar field records NameSilo, LLC; this is kept as an exact source value. The source stores 188.114.97.3 as the observed address in this record. The registration date for krakenx.top is recorded as 2026-09-24. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
Conclusion
The krakenx.top record states that VirusTotal recorded 3 detections among 91 scanners on 2026-09-25. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-25. PhishDestroy remains a separate publisher catalogue entry in the stored record. For krakenx.top, the registrar field records NameSilo, LLC; this remains separate from the other source fields. The observed address field in this record contains 188.114.97.3. The supported conclusion is bounded to the exact stored observations for krakenx.top. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to krakenx.top during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain krakenx.top as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to krakenx.top. The stored record does not justify extending that rule to 188.114.97.3 or to other infrastructure records.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='krakenx.top', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
DOM Analysisanalyzed 2026年9月25日score 98/1001 brand signal
Submitted URLhttp://krakenx.top/
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.
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 01:32:08 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-26 22:45:35 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-26 22:45:35 UTC → 2026-09-30 16:14:55 UTC · 89.49hmidpoint estimate ≈ 2026-09-28 19:30:15 UTC · precision low · 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
V
Vue.js
JavaScript frameworks
Vue.js is an open-source model–view–viewmodel JavaScript framework for building user interfaces and single-page applications.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
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.
Domain Status Transition2026-09-27 10:05:03 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-25 06:13:09 UTC
VirusTotal scanner detections updated from 1 to 3. Added scanner alerts: Forcepoint ThreatSeeker, LevelBlue.
Threat First Observed2026-09-25 05:40:33 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.97.3.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
17 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.
(US)
PhishDestroy Investigation
