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.
Analysis as of July 24, 2026 indicates that the domain kakaotalk.network is actively leveraged for generic phishing. The site was registered on February 21, 2026 through NiceNIC International Group Co., Limited and is hosted behind Cloudflare (AS13335) with the IP address 211.183.223.11 located in the United States. DNS resolution uses the Cloudflare name servers justin.ns.cloudflare.com and margot.ns.cloudflare.com. The HTTPS service presents a certificate issued by Google Trust Services under the WE1 name, confirming a valid TLS chain, while the web server returns HTTP status 521, indicating that Cloudflare is unable to connect to the origin server.
Page title retrieved from the site reads “카카오”, suggesting an attempt to reference the Korean messaging service, although the content of the page has not been examined. Security intelligence shows the domain appears on three blocklists and is explicitly blocked by PhishDestroy, MetaMask, and SEAL. VirusTotal scans reported two detections out of ninety‑three vendors, reinforcing the malicious classification. Gridinsoft assigns a trust score of 0 out of 100, and automated fingerprinting identified Cloudflare and HTTP/3 as the underlying technologies.
The domain remains listed as active. While the limited public data confirms the phishing intent, details such as the specific phishing kit, credential harvesting page, or victim targeting are not yet disclosed. Defenders should block the domain at network perimeter, update URL filtering lists with the known blocklist entries, and monitor for any outbound connections to the associated IP. Continuous scanning with multi‑engine services is advised to capture any changes in detection counts or additional malicious payloads.
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.
Attributionmechanism: Http 5xxsource: Current Http Probe
Evidence layersAvailability: UnreachableContent: UnknownDNS: ResolvedRegistration: Active
Latest HTTP observation未知Origin unreachableHttp 5xx20%2026-10-14 02:39:00 UTC
RDAP registration有效NICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765RDAP HTTP 200source: Rdap Status CollectorclientDeleteProhibitedclientTransferProhibitedexpires 2026-12-11 09:31:07 UTCchecked 2026-08-05 18:32:34 UTC
Observed timelinelast reachable: 2026-10-02 23:00:57 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.
技术 · 2 identified
Cloudflare
CDN
Web infrastructure and security company providing CDN, DDoS mitigation, and DNS 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.
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.
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.
(RU)
PhishDestroy Investigation
