VirusTotal
4 / 89
“AMLScore and AMLBot: Enhancing DeFi Compliance Solutions”
The domain amlcheckpro.digital is a confirmed phishing site engaged in brand impersonation targeting Binance users. It presents itself as a cryptocurrency compliance tool but is designed to harvest login credentials through a fraudulent interface, posing an elevated risk of account takeover. No cryptocurrency drainer kit was detected, and the site is currently taken offline.
Technical indicators confirm the malicious nature of amlcheckpro.digital. As of analysis, 2 of 95 VirusTotal security vendors flagged the domain, including CRDF and Gridinsoft, which assigned a trust score of 0/100. The domain was registered on 2026-02-21 via PDR Ltd. d/b/a PublicDomainRegistry.com and resolves to IP address 188.114.96.3, hosted on Cloudflare (AS13335). It appears on 2 security blocklists, PhishDestroy and ScamSniffer, though Google Safe Browsing has not flagged it. The SSL certificate is issued by Google Trust Services / WE1, and the observed page title was 'AMLScore and AMLBot: Enhancing DeFi Compliance Solutions'. Nameservers are john.ns.cloudflare.com and alexandra.ns.cloudflare.com.
Victims of amlcheckpro.digital should immediately change their Binance account password and enable two-factor authentication if credentials were entered. Monitor the account for unauthorized transactions and report any fraudulent activity to Binance support. The domain can be reported to Google Safe Browsing, PhishTank, and the registrar PDR Ltd. for further action. Users who interacted with the site should also check for unexpected browser extensions or malware and consider revoking any suspicious token approvals as a precaution.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/AML_GROUPStored page referencehttps://t.me/checkaml_supportStored page referenceIoC extraction recorded 2026-08-01 04:29:25 UTC
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginxScanner note: hosting_placeholder: raw=placeholder; http=200; via=https_direct; server=nginx
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.
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.
Edge-IP reputation is not attributed to this domain.
alexandra.ns.cloudflare.comLocation describes the IP network.
521d2eef6d079f7179863a231597d260e54e9691d3d3d0d9b0c91f600fb1236bSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
17 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
187 stored lookalike domains
Showing 100 of 187
Reported by 1 community member, first seen Sep 12, 2025
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive