The identity of the owner of the website is hidden on WHOIS The Tranco rank (how much traffic) is rather low Cryptocurrency services detected, these can be high risk The age of this site is (very) young.
We found a valid SSL certificate
証拠の概要
クリティカル
VirusTotal
10/89
OTX
13 community refs
URLScan
Stored capture
The domain amlbot.limited was observed delivering a crypto‑focused impersonation campaign targeting the AMLBot brand. Infrastructure analysis shows the domain resolving to the IP address 198.18.2.119, hosted without an SSL certificate, indicating that connections are unencrypted HTTP only. The site is currently offline, as confirmed by the latest status check, and has been removed from active service. Reputation metrics are uniformly negative: Gridinsoft assigns a trust score of 0 out of 100, while Scamadviser reports a modest 45 out of 100, reflecting limited confidence in the domain’s legitimacy.
The domain is listed on at least one public security blocklist and is explicitly blocked by the PhishDestroy sinkhole, confirming that defensive platforms have recognized it as malicious. AlienVault’s Open Threat Exchange references the domain in a single threat‑intel pulse, further corroborating its involvement in malicious activity. VirusTotal scans returned detections from 11 of 95 security vendors, providing independent confirmation of the domain’s malicious nature. The page title returned by the HTTP response is “amlbot.limited,” matching the domain name and offering no additional context about the content served.
The domain is identified as a crypto scam that impersonates AMLBot, but no further detail about the specific fraudulent payload or user‑interaction flow is publicly available. Defenders should ensure that traffic to 198.18.2.119 is blocked at network perimeters, add amlbot.limited to local and cloud‑based blocklists, and monitor inbound/outbound connections for any residual activity. Continued observation of DNS queries for the domain is advisable, as the lack of disclosed nameserver information may indicate the use of dynamic or fast‑flux infrastructure that could reappear under alternative hostnames.
DOM Analysisanalyzed 2026年4月23日score 98/1001 brand signal
Submitted URLhttps://amlbot.limited/
Favicon Hash
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.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-11 10:36:50 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:36:50 UTClast content: 2026-10-11 10:36:50 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.
Last analyzed Previous stored snapshot: 10 detections
alphaMountain.ai
BitDefender
CRDF
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
ソフォス
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.
10 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.
(US)
