On 2026-10-14, the domain tokenimnet-cdn-gw-hk27.cfd was listed on the OpenPhish blocklist, providing a dated external reference. VirusTotal also recorded detections for this domain on the same day.
Recorded Evidence
OpenPhish included tokenimnet-cdn-gw-hk27.cfd on its blocklist as of 2026-10-14. PhishDestroy documented an internal listing for the domain on 2026-10-14. VirusTotal checked the domain on 2026-10-14, recording 7 detections out of 92 total scanners. The domain was registered through Dynadot Inc on 2026-10-12.
Interpretation
The VirusTotal record contains a measurement of how many security scanners detected the domain on a specific date, providing insight into its recognition by multiple detection engines. The OpenPhish blocklist entry is an external listing that documents the domain's inclusion in a curated security source. These observations from OpenPhish, VirusTotal, and PhishDestroy offer a multi-source snapshot of the domain’s status shortly after its registration.
Recommended Actions
For any review of tokenimnet-cdn-gw-hk27.cfd, preserve the OpenPhish and PhishDestroy records as dated evidence for comparison with future blocklist entries. Retain the VirusTotal detection results to track changes in scanner recognition over time. Use these source records to inform ongoing monitoring and contextual analysis of the domain.
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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.
Latest HTTP observation未知Probe Inconclusive20%2026-10-14 19:45:45 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-14 19:45:45 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.
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
Archived HTTP responseHTTP 200
Requested URL:http://tokenimnet-cdn-gw-hk27.cfd/
imToken | Ethereum & Bitcoin Wallet
imToken ，一款安全放心、简单易用的数字钱包，超千万用户信赖. It supports BTC, ETH, BNB, TRX, DOT, MATIC, LTC, BCH, ATOM, OP, FIL, ARB, EOS, KSM, XTZ, CKB and many other tokens. It also allows you to swap token and use DApp right from the wallet
Values retained by the collector; long values may be shortened during collection.
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.
Threat First Observed2026-10-14 19:45:45 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 156.225.27.69.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
8 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.
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)
