This domain, amlbot.express, was registered on 2026-02-21 and is currently reported as offline. Intelligence indicates that the site is being used to impersonate the legitimate AMLBot brand in order to run a cryptocurrency-related scam. The domain appears on a single security blocklist and is actively blocked by the PhishDestroy service, confirming its malicious intent. VirusTotal analysis shows that 11 of 93 scanning engines flagged the domain, reflecting a moderate level of detection across independent scanners.
The Gridinsoft trust score for amlbot.express is 0 out of 100, which is the lowest possible rating and signals a high probability of malicious behavior. The only explicit classification available is “Crypto Scam,” aligning with the brand-impersonation motive. No public information is available regarding the registrar, hosting provider, IP address, SSL certificate details, Safe Browsing status, or Open Threat Exchange (OTX) references for this domain, and the page title has not been disclosed. Consequently, the infrastructure behind the domain remains opaque, limiting the ability to attribute the operation to a specific threat actor or to trace its hosting geography.
Defensive recommendations include adding amlbot.express to outbound and inbound blocklists across corporate firewalls, DNS filtering solutions, and endpoint protection platforms. Security teams should also monitor for re-registration attempts or the appearance of similar domains that mimic AMLBot, and consider sharing the indicator with threat-intel sharing groups to improve collective detection. Continuous re-evaluation is advised, as the domain could become active again or be used in new campaigns.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='amlbot.express', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
DOM Analysisanalyzed 2026年3月24日score 73/1001 brand signal
Impersonates
AMLBot
Latest Classified Outcome 2026-10-10 20:20:48 UTC
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:12:05 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-05-22 08:11:55 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-05-22 08:11:55 UTC → 2026-09-30 16:14:55 UTC · 3,152.05hmidpoint estimate ≈ 2026-07-27 00:13:25 UTC · precision very 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.
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
