Why this matters — ICANN RAA §3.18 obligation & victim-assistance
On PhishDestroy delivered an evidence-backed abuse report
(repeated 4 times, most recently ) to complaint@gname.com with VirusTotal detections, urlscan capture, legal violations, and full screenshot evidence.
More than 5 days later, the phishing infrastructure remains reachable
.
Under ICANN RAA §3.18 accredited registrars are contractually obliged to “take reasonable and prompt steps to investigate and respond appropriately to any reports of abuse.” Silence beyond 24 hours after a documented notification with verifiable evidence is not a timing issue — it is a policy decision to let the operation continue. PhishDestroy\'s position: where a registrar fails to act on clear evidence, the registrar has aligned itself with the operator of the scheme and bears co-responsibility for downstream harm caused to victims from the moment of notification onward.
Victim-assistance obligation. If Gname.com Pte. Ltd. doesn't consider the listed detections enough proof — that is interesting in itself, given the volume of independent vendor confirmations. But after 4 separate notifications over 5 days, with the operation still active, the registrar took no measurable action to mitigate the harm caused by their client. The reasonable next step is direct help to any identified victims — contact & payment-trail disclosure, abuse-thread transcripts, registrant data preservation — since the registrar chose, by inaction, to extend the window of damage.
amlcontrolbot[.]org
Absence of detections does not constitute assurance of safety, particularly given the recent creation date and active blocklist status. The domain’s risk posture is therefore classified as “under investigation” and its operational status is listed as active. No public SSL certificate details, HTTP response codes, or page‑title information have been disclosed, limiting visibility into the exact content served.
Consequently, the primary evidence supporting a malicious assessment consists of its presence on a blocklist, active blocking by PhishDestroy, and the typical use of short‑lived Cloudflare‑fronted domains in phishing campaigns. Defenders should consider adding amlcontrolbot[.]org to outbound‑web filtering rules, monitoring DNS queries for the domain, and correlating any internal traffic to the IP 172.67.137.4 with user activity logs. Ongoing observation is recommended to detect any future changes in detection vendor scores or additional blocklist listings that could further clarify the threat landscape surrounding this infrastructure.
Threat Response Pipeline
Public Blocklist Status
Evidence Capture
Gname.com Pte. Ltd.Domain Intelligence
(SG)
Technical detailsDNS, SSL SANs, timestamps
ICANN OVERSIGHT · FEE COLLECTED
ICANN Got Paid. Accountability Did Not Arrive.
ICANN Got Paid. Accountability Did Not Arrive.
For this gTLD, the registrar above operates under an ICANN contract. ICANN collects annual, variable and transaction-based fees tied to registrations, renewals and transfers.
Accreditation: monetized. Accountability: please check back later.
Then the magic starts: ICANN writes RAA §3.18, the registrar investigates abuse inside its own customer base, and victims deliver the evidence for free while every layer waits for someone else to act. If that makes victims feel safer, excellent—the invoice worked.
Technologies · 2 identified
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
www.cloudflare.com 100% confidence
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
httpwg.org 100% confidenceVirusTotal Analysis
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of amlcontrolbot.org · checked Jul 27, 2026
Evidence & External Reports
ChainPatrol
“I fell victim to a scam involving the website amlcontrolbot.org. The scammer tricked me into authorizing/sending funds via a smart contract interaction in my Trust Wallet. A total of 1474.91 USDT was transferred from my wallet to the scammer's TRON address: TMWzHTPSBYQV4PrWJxbf5HQXvQNmTVJyAC.”
Web-Check Were You Affected by This Site?
If you have interacted with this domain, entered personal information, or connected a cryptocurrency wallet — take immediate action. Below are resources to help you report the incident and protect yourself.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or generate an AI-powered complaint →
Related Domain Reports
More Domains at Gname 6 flagged
msxlkjis.us.cc 
imootken.top About This Report: amlcontrolbot.org
This report presents the latest stored evidence available to PhishDestroy. Source timestamps are shown where available; availability and vendor verdicts can change after collection.
amlcontrolbot.org has been flagged by 3 security vendors as of August 1, 2026.
If you believe this listing is inaccurate, you can submit an appeal. For more information about our methodology, visit our FAQ page.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive
Recommendations & Advice for Victims
An estimated $51 billion flowed to illicit crypto wallets in 2024 (source). If you interacted with amlcontrolbot.org — act now.
What should I do immediately?
Urgent
- Revoke token approvals — use revoke.cash to remove access granted to malicious smart contracts
- Move remaining funds to a brand-new wallet. The compromised wallet is no longer safe
- Change all passwords — email, exchange accounts, anything that shares the same password
- Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
- Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
According to the FBI, the most important details are transaction data:
- Cryptocurrency addresses — scammer's wallet (e.g.,
0x5856...35985) - Amount & crypto type — exact amount (e.g., 1.02345 ETH, 0.5 BTC, 500 USDT)
- Transaction ID (hash) — the unique blockchain transaction identifier
- Exact dates & times — of each transaction and first contact with scammer
- Screenshots — scam website, chat messages, emails, wallet transactions, social media
- All URLs & domains used by the scammer (including
amlcontrolbot.org) - Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
- FBI IC3 — Internet Crime Complaint Center (US federal reporting)
- Europol — European cybercrime reporting (EU)
- Chainabuse — flag scam wallets across exchanges & platforms
- Your crypto exchange — contact Coinbase/Binance/Kraken support to freeze scammer's address
- Local police — creates an official record, even if they can't act immediately
The FBI recovered over $1 billion in crypto fraud in 2024 thanks to victim reports. Your report matters.
How do crypto scams typically work?
- Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
- Malicious approvals — "connect wallet" prompts that grant unlimited token spending to attackers
- Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
- Recovery scams — victims targeted AGAIN by fake "recovery agents" demanding upfront fees. Always a scam
- Fake ads & airdrops — Google/social media ads and "free token" offers leading to wallet drainers
- AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
- Use a hardware wallet (Ledger, Trezor). Never store large amounts in browser wallets
- Bookmark official sites — never click links from emails, DMs, or ads
- Read every approval — verify permissions before signing. Reject unlimited approvals
- Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
- "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
How big is the crypto scam problem?
- $51 billion flowed to illicit crypto wallets in 2024 — CoinLedger
- Pig butchering losses grew 40% year over year, now the fastest-growing fraud type
- Only ~5% of victims report — your report helps shut down criminal networks
- FBI recovered $1B+ in 2024 thanks to victim reports — FBI.gov
Sources: FBI · CoinLedger · WorldMetrics