The domain amlwallet.report is a confirmed brand impersonation phishing domain targeting the cryptocurrency compliance platform AMLBot. It posed as an AML Check service, using the page title 'AML Check - The full-fledged crypto compliance solution' to trick users into believing it was a legitimate compliance tool. The specific threat type is brand impersonation, and no drainer kit was identified. The domain is currently taken offline, but it posed a risk of credential theft or financial fraud for users seeking AMLBot services.
Technical indicators for amlwallet.report include a detection rate of 2 of 95 VirusTotal vendors, with flags from alphaMountain.ai and Forcepoint ThreatSeeker. The domain was registered on February 21, 2026, through Web Commerce Communications Limited, and resolves to IP address 2.59.163.70, located in Poland (AS215540 GLOBAL CONNECTIVITY SOLUTIONS LLP). It appears on 4 security blocklists: PhishDestroy, Polkadot, Enkrypt, and Codeesura. Google Safe Browsing did not flag the domain, and no SSL certificate was issued. The nameservers are naya.ns.cloudflare.com and howard.ns.cloudflare.com.
As amlwallet.report is now offline, immediate action is not required, but users who interacted with the site should change any passwords entered, enable two-factor authentication on associated accounts, and monitor for unauthorized activity. Since no drainer kit was found, token approval revocation is not necessary, but users should remain vigilant. To report similar phishing domains, contact the impersonated brand AMLBot directly and submit the domain to security blocklists like PhishDestroy.
Extracted from stored page analysis
Observed indicators
0 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='amlwallet.report', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
DOM Analysisanalyzed 2026年7月29日score 63/1001 brand signal
IoC Extractionscanned 2026年8月1日0 wallet · 1 Telegram IoC
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:08:01 UTC
RDAP registration不明
Observed timelinecurrent episode first observed: 2026-09-30 16:14:55 UTCfirst terminal observation: 2026-09-30 16:14:55 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.
11 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.
(MY)
