Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@kurun.com.
The latest stored availability evidence still shows the domain reachable; 6 months 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.
imtoken[.]xn--fiqs8s
“530”
imtoken.xn--fiqs8s was registered on 21 February 2026 through the registrar 成都西维数码科技有限公司. The domain is configured with the authoritative nameservers ns1.363.hk and ns2.363.hk and resolves to the IPv4 address 45.205.26.173, which belongs to AS8796 FASTNET DATA INC and is geolocated in the United States. No TLS certificate is presented for the host, indicating that connections are served over plain HTTP only. The page title retrieved during the brief scan is the string “530”, providing no further context about the page’s purpose. VirusTotal analysis shows that seven of ninety‑three antivirus and URL scanning engines flagged the domain as malicious, and Gridinsoft assigned a trust score of zero out of one hundred.
The domain is listed on a single external security blocklist and has been actively blocked by the PhishDestroy service. Intelligence tags the site as a crypto‑related scam that impersonates the brand “celer”, aligning with the broader threat category of brand impersonation. Current operational status is reported as offline, suggesting that the hosting infrastructure has been taken down or is no longer serving content at the time of observation. The available evidence confirms that the infrastructure is deliberately associated with a brand‑impersonation campaign targeting users of the celer brand, likely to harvest cryptocurrency credentials or funds.
However, the lack of a TLS certificate, the minimal page title, and the relatively low number of vendor detections leave open questions about the full scope of the malicious payload and whether additional phishing pages exist under the same IP address. Defenders should add 45.205.26.173 to network‑level deny lists, enforce DNS filtering for imtoken.xn--fiqs8s, and monitor the associated nameservers (ns1.363.hk, ns2.363.hk) for any re‑registration activity.
Network Security Intelligence
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Cloudflare DNS | imtk9lc.com |
malicious | Sinkholed |
| DNS4EU | imtk9lc.com |
malicious | Sinkholed |
| Cloudflare DNS | 02458454xyz.imtoken1.bmxuij.cn |
malicious | Sinkholed |
| OpenDNS | 02458454xyz.imtoken1.bmxuij.cn |
phishing | Phishing Block |
| DNS4EU | 02458454xyz.imtoken1.bmxuij.cn |
malicious | Sinkholed |
| Cloudflare DNS | vccxrfo3.imtoken.bmxuij.cn |
malicious | Sinkholed |
| OpenDNS | vccxrfo3.imtoken.bmxuij.cn |
phishing | Phishing Block |
| DNS4EU | vccxrfo3.imtoken.bmxuij.cn |
malicious | Sinkholed |
Threat Response Pipeline
Public Blocklist Status
VirusTotal Analysis
Archived Evidence
Evidence & External Reports
PD-20260203-C94F64 Recipient: abuse@kurun.com Were You Affected by This Site?
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive