The domain clarifytokens.digital presents a page titled "AML CHECK" and is classified as a cryptocurrency scam. It impersonates the brand OKX, posing as a compliance or verification service. The threat involves tricking users into submitting sensitive information or cryptocurrency credentials under the guise of an anti-money laundering check, potentially leading to financial theft or account compromise.
Technical analysis confirms 15 out of 95 VirusTotal vendors flagged the domain as malicious, including ADMINUSLabs, alphaMountain.ai, BitDefender, CRDF, and CyRadar. One blocklist entry exists. The domain was registered on 2025-01-03 via Web Commerce Communications Limited and is hosted on IP 104.21.71.171 (US), assigned to AS13335 Cloudflare, Inc. SSL is issued by Google Trust Services / WE1, and nameservers are anita.ns.cloudflare.com and keaton.ns.cloudflare.com.
The domain is currently BANNED, indicating active mitigation. The risk level is high due to the impersonation of a legitimate cryptocurrency exchange and the specific scam type targeting financial assets. Users should avoid interaction and report any related activity.
Extracted from stored page analysis
Observed indicators
0 wallet · 2 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
DOM Analysisanalyzed 2026年4月11日score 78/1001 brand signal
IoC Extractionscanned 2026年8月2日0 wallet · 2 Telegram IoCs
Submitted URLhttps://clarifytokens.digital/
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Observed timelinelast reachable: 2026-09-15 22:17:52 UTCcurrent episode first observed: 2026-10-01 01:40:33 UTCobserved RIP window: 2026-09-15 22:17:52 UTC → 2026-10-01 01:40:33 UTC · 363.38hmidpoint estimate ≈ 2026-09-23 11:59:12 UTC · precision 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.
使用技術 · 1 identified
Cloudflare
CDN
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
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.
16 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.
Web Archive
Preserved in ウェイバック・マシン — historical evidence archived
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)
