The domain amlcheck.giving is a phishing site engaged in brand impersonation targeting the CSGO community. It presents itself as an 'AML Check' page to deceive users into disclosing cryptocurrency-related credentials or performing transactions under false pretenses. No drainer kit was identified, but the site operates as a cryptocurrency scam. As of the latest verification, amlcheck.giving has been taken offline.
Technical indicators confirm the elevated risk. The domain is flagged by 2 of 95 VirusTotal security vendors, including Gridinsoft and SOCRadar, with a Gridinsoft trust score of 0/100. It appears on 5 security blocklists, including PhishDestroy, ScamSniffer, and Polkadot. Registered through Web Commerce Communications Limited on October 24, 2025, amlcheck.giving resolves to the IP address 185.178.208.137, hosted by AS57724 (DDOS-GUARD LTD) in Russia. No SSL certificate is present, and the observed page title is 'AML Check'. Nameservers are augustus.ns.cloudflare.com and eve.ns.cloudflare.com.
Users who interacted with amlcheck.giving should immediately revoke any token approvals granted to unknown contracts and transfer remaining funds to a new, secure wallet. Enable two-factor authentication on all cryptocurrency and gaming accounts, and monitor for unauthorized transactions. Report the domain to relevant platforms, including the impersonated brand (CSGO), and submit the URL to anti-phishing databases such as Google Safe Browsing, PhishTank, or the Anti-Phishing Working Group.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='amlcheck.giving', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
DOM Analysisanalyzed 2026年3月24日score 10/1007 brand signals
IoC Extractionscanned 2026年8月2日0 wallet · 1 Telegram IoC
Submitted URLhttp://amlcheck.giving/
ICANN OVERSIGHT
認定と RAA の背景
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.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 01:08:16 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-04-22 17:25:09 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-22 17:25:09 UTC → 2026-09-30 16:14:55 UTC · 3,862.83hmidpoint estimate ≈ 2026-07-12 04:50:02 UTC · precision very low · basis bounded
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.
13 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.
(MY)
