Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
On July 24, 2026, the domain onionblog.online was observed to host a page with the title “Кракен даркнет вход - Кракен даркнет вход”. The title explicitly references the Kraken brand, confirming the intelligence label of a brand‑impersonation campaign targeting Kraken users. The domain was registered on 28 June 2025 through NiceNIC International Group Co., Limited and is hosted on Cloudflare infrastructure (nameservers burt.ns.cloudflare.com and malavika.ns.cloudflare.com). DNS resolution returns the IP address 172.67.202.97, which belongs to AS13335 Cloudflare, Inc., and is geolocated to the United States. No TLS certificate was presented, indicating that the site was served over plain HTTP.
VirusTotal reports that 2 of 95 scanning engines flagged the domain, confirming malicious intent without specifying detection categories. The domain appears on a single external blocklist and has been actively blocked by the PhishDestroy sinkhole. Gridinsoft assigns a trust score of 0 out of 100, reinforcing the malicious assessment. The current HTTP status is offline, suggesting that the site has been taken down or is otherwise unreachable. While the exact content of the landing page has not been captured, the combination of a brand‑specific title, the lack of encryption, low trust score, and multiple vendor detections provides strong evidence of a credential‑harvesting operation aimed at Kraken users.
Uncertainty remains regarding the full scope of the phishing kit, any associated command‑and‑control infrastructure, and whether additional domains share the same infrastructure. Defenders should block or sinkhole 172.67.202.97 and add onionblog.online to local blacklists. Email and web gateway filters should be updated to detect the brand‑impersonation pattern, and users of Kraken services should be warned not to enter credentials on sites lacking a valid TLS certificate.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='onionblog.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
What we count
Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Unverified.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedDec 16, 2025
DOM Analysisanalyzed Apr 23, 2026score 10/1002 brand signals
Submitted URLhttp://onionblog.online/
ICANN OVERSIGHT
Accreditation and RAA context
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.
Primary outcomeInactivereason: Not registered in RDAP90% confidence
Attributionmechanism: Rdap 404source: Rdap Status Collector
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Not registered
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-14 10:54:41 UTC
RDAP registrationNot registeredRDAP HTTP 404source: Rdap Status Collectorexpires 2027-06-28 23:59:59 UTCchecked 2026-10-14 04:15:20 UTC
Registrar action markerverified clientHold markerNICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765causal link to our report not established
Observed timelinelast reachable: 2026-06-14 22:41:18 UTCcurrent episode first observed: 2026-08-05 01:45:38 UTCobserved RIP window: 2026-06-14 22:41:18 UTC → 2026-08-05 01:45:38 UTC · 1,227.07hmidpoint estimate ≈ 2026-07-10 12:13:28 UTC · precision very 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.
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.
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
onionblog.online detected and queued for full analysis
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.
5 evidence signal groups linked0 reports recordedUnverified
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · onionblog.online
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
(RU)
PhishDestroy Investigation
