imtoken.surf was documented by VirusTotal on 2026-10-09 with 14 detections out of 92 scanners, providing a dated record of its detection status. The domain also appeared in four OTX pulses as of 2026-10-13, reflecting its presence in external intelligence feeds.
Recorded Evidence
VirusTotal scanned imtoken.surf on 2026-10-09, recording 14 detections from 92 total scanners. OTX referenced the domain in four distinct pulses as of 2026-10-13. PhishDestroy included an internal listing for imtoken.surf on 2026-10-13. The domain was registered with NameMart Pte. Ltd. on 2026-08-20.
Interpretation
PhishDestroy contains an internal catalogue entry for imtoken.surf, documenting its listing status on a specific date. VirusTotal provides a measurement of how multiple security vendors classified the domain at the time of its scan. OTX records the domain’s references in community-driven intelligence, offering context on its external visibility.
Recommended Actions
For imtoken.surf, retain the VirusTotal, OTX, and PhishDestroy records as reference points for future analysis. Compare any subsequent scans or catalogue entries to these records to track changes in detection or listing status. Use these dated observations when conducting technical or security reviews involving the domain.
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-13 13:28:34 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-13 13:28:34 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.
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-13 13:28:34 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 186.240.200.15.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
9 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.
PDF notice generated Notice text archived (846 chars)
Abuse notice text as sent to the provider
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (SG):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and SG's domestic fraud laws.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
(SG)
