This domain is flagged as an elevated-risk brand impersonation threat specifically targeting Binance, a major cryptocurrency exchange platform. Analysis indicates the site was designed to deceive users into believing they were interacting with legitimate Binance compliance tools, likely to harvest credentials, personal data, or facilitate unauthorized transactions under the guise of anti-money laundering (AML) verification processes. Infrastructure analysis reveals multiple high-confidence indicators of malicious activity. The domain www.secureaml.net, registered on September 02, 2025, through NameCheap, Inc., resolves to the IP address 64.29.17.1. It is currently offline but was previously detected by four security blocklists, including Polkadot, Codeesura, PhishDestroy, and Enkrypt. The Gridinsoft trust score for this domain is 0/100, reflecting an absence of legitimate reputation. VirusTotal reports that 1 out of 95 security vendors flagged this domain as malicious, with the page title "AMLBot - The full-fledged crypto compliance solution" serving as a key deception vector to mimic Binance’s official compliance tools. To mitigate risks associated with this brand impersonation threat, affected organizations and users should immediately revoke any credentials potentially exposed through interaction with this domain. Network-level protections should be implemented to block traffic to 64.29.17.1 and any associated subdomains. Security teams are advised to monitor for phishing campaigns referencing AML or compliance workflows, particularly those targeting cryptocurrency users. Domain registrars and hosting providers should be notified of the fraudulent infrastructure to prevent re-activation. Users should verify all communications through official Binance channels and enable multi-factor authentication on all cryptocurrency-related accounts to reduce the impact of credential theft.
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='duplicate-disabled-4420.invalid', port=80): Max retries exceeded with url: / (Caused by Ne
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
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 DetectedSep 9, 2025
DOM Analysisanalyzed Apr 24, 2026score 10/1006 brand signals
Submitted URLhttps://www.secureaml.net/
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 observationUnknownProbe Inconclusive20%2026-10-11 01:10:56 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-06-09 22:22:32 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.
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
duplicate-disabled-4420.invalid 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 7, 2026
Time to First Unavailability
5749 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.
4 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 →
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.
(US)
