Analysis of amlsecure.report indicates that the domain is being used for credential phishing, specifically targeting users of anti‑money‑laundering services. The site was created on 14 December 2025 and is currently taken offline, but historical evidence shows it was actively serving malicious content. The page title observed during its active period was "The Best AML Service for Your Business - AML Secure," suggesting an attempt to lure victims with a legitimate‑sounding offering. The domain resolves to IP address 188.114.97.3, which is hosted by Cloudflare (AS13335) in the United States.
No SSL certificate was presented, leaving the connection unencrypted and making the site easier to intercept or tamper with. Reputation data is extremely poor: Gridinsoft assigns a trust score of 0 out of 100, and the domain appears on five security blocklists. Detection services have flagged the domain, with two of ninety‑five VirusTotal scanners raising alerts, and it is explicitly blocked by PhishDestroy, ScamSniffer, Polkadot, Enkrypt, and Codeesura. The registrar listed is Global Domain Group LLC, and the authoritative nameservers are augustus.ns.cloudflare.com and eve.ns.cloudflare.com.
While the exact phishing payload and credential collection mechanisms have not been captured, the combination of a targeted page title, lack of TLS, low trust rating, and multiple blocklist entries strongly indicates a credential‑phishing operation. Defenders should add amlsecure.report to firewall and proxy block lists, monitor DNS queries for the domain and its associated IP, and enforce TLS inspection policies to detect any future attempts to host similar content. Continuous observation of the Cloudflare IP range for related activity is advised, as threat actors may shift to new subdomains under the same hosting infrastructure.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='amlsecure.report', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
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.
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 01:16:30 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-15 22:17:48 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: 3 detections
alphaMountain.ai
CRDF
Gridinsoft
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.
(US)
