Security engines reporting a detection: 5. Public blocklists reporting a match: 4. Exercise extreme caution — do not enter credentials or personal information.
The owner of the website is using a service to hide their identity on WHOIS According to Tranco this site has a low rank This website is (very) young.
The SSL certificate is valid This website is safe according to DNSFilter
Evidence Summary
Critical
VirusTotal
5/91
URLScan
Stored capture
Analysis of the domain amlsecure.blog, observed as offline at the time of reporting on July 25 2026, indicates that it was used for credential phishing aligned with a crypto‑related scam. The site was registered on October 29 2025 through Web Commerce Communications Limited, a registrar frequently associated with malicious registrations. No SSL certificate was presented, leaving the connection unencrypted. The authoritative nameservers are augustus.ns.cloudflare.com and eve.ns.cloudflare.com, pointing to Cloudflare’s DNS service. DNS resolution returned the IP address 172.67.141.15, which belongs to AS13335 Cloudflare, Inc. located in the United States.
The page title retrieved from the site reads “The Best AML Service for Your Business – AML Secure,” suggesting a fraudulent attempt to lure victims interested in anti‑money‑laundering services. Reputation services rate the domain extremely poorly: Scamadviser assigns a trust score of 1/100, Gridinsoft 0/100, and the domain appears on five security blocklists. VirusTotal scans reported four detections out of ninety‑five vendors, confirming malicious activity. The site is also listed on blocklists operated by PhishDestroy, ScamSniffer, Polkadot, Enkrypt, and Codeesura.
The combined evidence points to a credential‑phishing infrastructure targeting users seeking crypto or AML solutions. Uncertainty remains regarding the exact phishing kit or any additional payloads, as no content analysis beyond the title is available. Defenders should block the domain and its associated IP at perimeter defenses, update URL filtering rules, and monitor for any future re‑use of the Cloudflare IP range. Incident responders should also inspect logs for traffic to amlsecure.blog and consider tightening controls around AML‑related communications to mitigate potential credential compromise.
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.
RegistrationCreated Oct 29, 2025 (344d)—Expires Oct 29, 2026
HTTP Status502 Error
Time to First Unavailability186 days
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 DetectedNov 3, 2025
DOM Analysisanalyzed Apr 23, 2026score 75/100
Submitted URLhttp://amlsecure.blog/
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.
Latest HTTP observationUnknownOrigin unreachableHttp 5xx20%2026-10-07 01:47:55 UTC
RDAP registrationUnknown
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.
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.
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
amlsecure.blog 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.
May 9, 2026
Time to First Unavailability
4475 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 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 · amlsecure.blog
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.
Content matches4
Same favicon hash or the same page title as this host.
(MY)
