VirusTotal
0 / 92
engines flag the domain
“onkeyon”
0 / 92
engines flag the domain
No threat flag
Not on Google threat lists at check time
0
threat pulses mention the domain
Online · HTTP 200
Cloudflare · 172.67.149.67 · TLS: Google Trust Services
Each check shows its own collection time. Zero detections do not guarantee safety.
ブロックリスト掲載ドメイン: usdc033.com — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 2/92 (Forcepoint ThreatSeeker, LevelBlue); PhishDestroy score 66/100. レジストラ: Gname.
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
2 / 92 engine detections
レポートを開く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
usdc033.com is a domain on the PhishDestroy blocklist. Its name pairs the USDC stablecoin ticker with a number, while the page itself carried the unrelated title "onkeyon". PhishDestroy first flagged it on 2026-10-09. The site has been offline since 2026-10-14, and as of 2026-10-19 its content is blocked by the hosting provider.
No specific scheme has been confirmed for this domain, so the risk comes from how it looks. A stablecoin ticker followed by a serial number is a naming style built to appear official to people holding or moving USDC. Domains like this can ask visitors to connect a wallet, sign a transaction or send funds, and any of those can cost the victim their tokens. The page title "onkeyon" does not mention USDC, so the title and the domain name do not match.
Independent detection is thin. On 2026-10-13, 2 of 92 VirusTotal engines flagged the domain: Forcepoint ThreatSeeker and LevelBlue. Most engines staying silent is common for new crypto lures, and it should not be read as a clean bill of health. The domain also appears in 4 AlienVault OTX pulses, which means other researchers have tied it to threat activity. PhishDestroy is the only blocklist listing it.
The domain was registered on 2025-12-29 through Gname.com Pte. Ltd. That is more than nine months before PhishDestroy detected it, so it was not a throwaway created the same week. It sits behind Cloudflare, Inc. on an address geolocated to Canada, and that front hides the real origin server. Its Google Trust Services WE1 certificate is the automated kind issued to Cloudflare-fronted sites, so the browser padlock says nothing about whether the site can be trusted.
If you connected a wallet on this site, review your token approvals and revoke any you do not recognise. Move remaining USDC and other assets to a fresh wallet if you signed anything you did not fully understand. Never enter a seed phrase or private key on a site reached through a stablecoin-themed domain. Defenders should block usdc033.com at DNS and proxy level, search logs for visits since 2026-10-09, and watch for similarly numbered USDC domains.
Edge-IP の評判はこのドメインに起因しません。
drake.ns.cloudflare.comsofia.ns.cloudflare.comLocation describes the IP network.
54cb26b0f65148bb3630c4a5e97a4d4be0b7e34d72dbef7316bea20218c66612Saved 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.usdc033.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of usdc033.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
usdc033.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
到達可能
2/92 engine detections
View sourceNo threat flag
View source4 community references
View sourceusdc033.com
View sourcePage captured
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
usdc033.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.