The domain amlbotscan.digital has been identified as a brand impersonation threat, specifically targeting AMLBot, with no known drainer kit associated. This domain was flagged due to its suspicious behavior and registration details, including a VirusTotal score of 1/95, registration through Web Commerce Communications Limited, resolution to IP 104.21.21.180, and creation date of February 21, 2026, it also appears on 1 security blocklist and has a Google Trust Services SSL certificate.
PhishDestroy identifies this domain as an active threat, with an elevated risk level, and recommends that users exercise caution when interacting with it, as the threat is still ongoing and poses a significant risk to users who may be tricked into divulging sensitive information or installing malicious software, it is essential to verify the authenticity of websites before providing any personal or financial information to avoid potential harm.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='amlbotscan.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
DOM Analysisanalyzed 2026年7月29日score 61/1001 brand signal
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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:27 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-03-15 05:15:31 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-03-15 05:15:31 UTC → 2026-09-30 16:14:55 UTC · 4,786.99hmidpoint estimate ≈ 2026-06-22 22:45:13 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.
技术 · 3 identified
Cloudflare Browser Insights
AnalyticsRUM
Performance monitoring tool that measures website speed from real users.
Google PageSpeed Insights — mobile performance audit of amlbotscan.digital· checked Mar 2, 2026
70
Needs Work
Performance
FCP
1.63s
First Contentful Paint
LCP
3.84s
Largest Contentful Paint
CLS
0.006
Cumulative Layout Shift
TBT
700ms
Total Blocking Time
SI
1.63s
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.
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)
