VirusTotal
4 / 92 engine detections
レポートを開く“Home”
The sent-report ledger records the first outgoing report at .
The recorded recipient is complaint@gname.com.
The latest stored availability evidence still shows the domain reachable; 11 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Googleなりすまし: usdc321.com — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 4/92 (Forcepoint ThreatSeeker, Gridinsoft, LevelBlue, SOCRadar); PhishDestroy score…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
4 / 92 engine detections
レポートを開くScan report
レポートを開く4 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
usdc321.com is an impersonation phishing page whose domain borrows the USDC stablecoin name, padded with a number so it looks like an official or promotional variant. It targets crypto users who hold or want USDC. PhishDestroy first flagged it on 2026-10-09. The site went offline on 2026-10-14, its content is blocked at the provider, and it was still down when last checked on 2026-10-19.
Sites that pose as a stablecoin brand usually present themselves as an official portal, reward program or yield service. They then push visitors to connect a wallet, sign a transaction, send USDC to a deposit address, or type in a recovery phrase. Whatever the victim hands over goes straight to the operators, and on-chain transfers cannot be reversed. The page itself was titled only "Home", which carries no brand cue, while the domain name and our classification point to USDC impersonation.
On 2026-10-13, 4 of 92 VirusTotal engines flagged the domain: Forcepoint ThreatSeeker, Gridinsoft, LevelBlue and SOCRadar. That is low coverage, so most security tools would have let it through. The domain also appears in 4 AlienVault OTX pulses, which means other researchers have tied it to malicious activity independently. PhishDestroy is the only blocklist carrying it.
The domain was registered through Gname.com Pte. Ltd. on 2025-11-09, about eleven months before PhishDestroy caught it. Registering a name and leaving it unused for that long is a common way to let a domain build age before a campaign starts. The site was served through Cloudflare, Inc. at 188.114.96.3 with a Canada geolocation, so the operators' real origin server is hidden behind the proxy.
If you sent USDC or any other token to an address shown on this site, record the transaction hash and report it to the exchange or wallet provider involved. Do not pay anyone who offers to recover the funds, because these offers are almost always a second scam. If you connected a wallet or signed anything, revoke the token approvals you granted and move your remaining assets to a fresh wallet. If you typed in a recovery phrase, treat that wallet as fully compromised. Defenders should block usdc321.com and watch for similar names that pair USDC with numbers.
Edge-IP の評判はこのドメインに起因しません。
drake.ns.cloudflare.comsofia.ns.cloudflare.comLocation describes the IP network.
b4156e5472d5ffcaa9d3c4d9b872e6fd01faa04381c86b32689fdb7d13732643Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.usdc321.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of usdc321.com · checked Oct 9, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
usdc321.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
live_content→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
到達可能→利用不可
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
到達可能
No threat flag
View source4/92 engine detections
View source4 community references
View sourcePD-20261009-C9F948
usdc321.com
View sourcePage captured
View sourcePD-20261009-C9F948 Recipient: complaint@gname.com Registrar: Gname.com Pte. Ltd. (Singapore) Policy Violations: Illegal Activities section forbids phishing, fraud, fake sites, malware distribution; registrar investigates and may suspend or delete domain Applicable Laws: Computer Misuse Act 1993 §§3+, Penal Code §§415–420 (cheating), Online Criminal Harms Act (OCHA)
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
usdc321.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.