This domain is flagged as a high-risk phishing threat targeting financial institutions and cryptocurrency services under the guise of anti-money laundering (AML) compliance verification. Analysis indicates the domain is designed to harvest credentials, sensitive financial data, or deploy malicious payloads through fake regulatory portals. The specific threat type involves brand impersonation of legitimate AML monitoring tools, likely exploiting trust in compliance procedures to deceive victims into submitting confidential information or executing unauthorized transactions. Infrastructure analysis reveals the domain amlbot.network was registered on May 17, 2026, through PDR Ltd. d/b/a PublicDomainRegistry.com. It currently resolves to the IP address 188.114.97.3 and utilizes a Let's Encrypt SSL certificate to present a false sense of legitimacy. VirusTotal detection metrics show 3 out of 95 security vendors have flagged this domain as malicious, indicating early-stage detection with potential for increased scrutiny. The domain remains active with no observed presence on major blocklists, suggesting it may still be in the initial deployment phase of its malicious campaign. Mitigation steps for organizations and users include immediate blocking of the domain and its resolving IP at the network perimeter. Security teams should monitor for any outbound connections to 188.114.97.3 and review logs for interactions with amlbot.network. Endpoint protection should be configured to detect and prevent access to newly registered domains impersonating compliance platforms. Financial institutions are advised to implement multi-factor authentication for all AML-related portals and conduct user awareness training to recognize phishing attempts leveraging regulatory compliance themes. Incident response protocols should include verification of any unexpected AML compliance requests through established secure channels.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='amlbot.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
RegistrationCreated May 17, 2026 (147d)—Expires May 17, 2027
Time to First Unavailability5h
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 DetectedJun 29, 2026
DOM Analysisanalyzed Jun 29, 2026score 71/1001 brand signal
Submitted URLhttps://amlbot.network/
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:07:56 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-07-05 16:18:18 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-05 16:18:18 UTC → 2026-09-30 16:14:55 UTC · 2,087.94hmidpoint estimate ≈ 2026-08-18 04:16:36 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.
Technologies · 6 identified
V
Vue.js
JavaScript frameworks
Vue.js is an open-source model–view–viewmodel JavaScript framework for building user interfaces and single-page applications.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Google PageSpeed Insights — mobile performance audit of amlbot.network· checked Jun 29, 2026
57
Needs Work
Performance
FCP
7.31s
First Contentful Paint
LCP
8.63s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
92ms
Total Blocking Time
SI
7.31s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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.
VirusTotal Detections Update2026-06-28 23:04:13 UTC
VirusTotal scanner detections updated from 0 to 3. Added scanner alerts: CRDF, Gridinsoft, alphaMountain.ai.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
amlbot.network detected and queued for full analysis
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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Jun 29, 2026
Time to First Unavailability
5 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.
5 evidence signal groups linked1 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.network
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.
