According to Tranco this site has a low rank This website may offer high-risk cryptocurrency services This website is (very) young.
The SSL certificate is valid This website is safe according to DNSFilter
证据摘要
关键
VirusTotal
3/91
URLScan
Stored capture
The domain aml.support is a confirmed phishing site engaged in brand impersonation targeting LinkedIn users. It presents itself as a cryptocurrency compliance solution under the false pretense of 'AML Check - The full-fledged crypto compliance solution', but its actual purpose is to deceive victims through credential phishing and cryptocurrency-related scams. No drainer kit was identified, and the site is currently taken offline, though it remains a documented threat.
Technical analysis of aml.support reveals limited but notable detection. The domain is flagged by 1 of 95 VirusTotal security vendors, including Gridinsoft, which assigned it a trust score of 0 out of 100. It appears on 4 security blocklists: PhishDestroy, Polkadot, Enkrypt, and Codeesura. The domain resolves to the IP address 212.34.150.32, hosted in the Netherlands under AS216071 SERVERS TECH FZCO. No SSL certificate is present, and the registrar and creation date are not available. MX records point to mx.zoho.eu and mx2.zoho.eu with priorities 10 and 20, respectively, while nameservers remain unknown.
Individuals who interacted with aml.support should immediately change any credentials entered on the site, particularly LinkedIn passwords, and enable two-factor authentication. Monitor accounts for unauthorized access or fraudulent activity. Cryptocurrency users should review wallet permissions and revoke any suspicious token approvals. Report the domain to relevant platforms such as Google Safe Browsing, the impersonated brand (LinkedIn), and local cybersecurity authorities to aid in takedown efforts and prevent further victimization.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
Telegram
https://t.me/AML_GROUPStored page reference
IoC extraction recorded 2026-08-01 04:05:14 UTC
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='aml.support', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 01:14:46 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-15 22:17:48 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.
Last analyzed Previous stored snapshot: 4 detections
alphaMountain.ai
Gridinsoft
SOCRadar
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.
12 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.
