This site, amlbot.services, presents itself as a free cryptocurrency anti-money laundering (AML) check tool, as indicated by its page title "Free AML Crypto Check – USDT, TRC20, ETH, TON, BTC." It impersonates a brand across the cryptocurrency compliance sector and is classified as a cryptocurrency scam. The primary threat is that it likely functions as a phishing or credential-harvesting site, tricking users into entering sensitive wallet or transaction data under the guise of a security check.
Technical evidence shows the site was flagged by 13 out of 95 VirusTotal vendors, with detections from ADMINUSLabs, alphaMountain.ai, BitDefender, CRDF, and CyRadar. It is hosted on IP address 104.21.112.1, located in the United States, and associated with AS13335 (Cloudflare, Inc.). The domain was registered through NameCheap, Inc. on 2025-06-26, and has no SSL certificate. It appears on 3 blocklists.
The site is currently down or offline. Its GridinSoft trust rating is 0 out of 100, and its DOM risk score is 10, indicating a high risk. The combination of low trust, high risk score, and multiple security vendor flags confirms this domain is malicious and should be avoided.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='amlbot.services', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
DOM Analysisanalyzed 2026年4月23日score 88/1002 brand signals
Submitted URLhttps://amlbot.services/
Favicon Hash
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
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.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 01:00:17 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-26 10:02:12 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-26 10:02:12 UTC → 2026-09-30 16:14:55 UTC · 102.21hmidpoint estimate ≈ 2026-09-28 13:08:33 UTC · precision low · basis bounded
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.
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.
13 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.
(US)
