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.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedFeb 26, 2026
DOM Analysisanalyzed Mar 24, 2026score 73/1001 brand signal
Impersonates
AMLBot
Latest Classified Outcome 2026-10-10 20:20:48 UTC
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:12:05 UTC
RDAP registrationUnknown
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.
Threat Ingested
amlbot.express detected and queued for full analysis
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Apr 23, 2026
Time to First Unavailability
1331 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
4 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · amlbot.express
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
