Google Safe Browsing
No threat flag
Not on Google threat lists at check time
“onkeyon”
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.
No threat flag
Not on Google threat lists at check time
Online · HTTP 200
Cloudflare · 188.114.97.1
Each check shows its own collection time. Zero detections do not guarantee safety.
ブロックリスト掲載ドメイン: usdc556.com — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 1/92 (LevelBlue); PhishDestroy score 66/100. レジストラ: Gname.
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
1 / 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
usdc556.com is on the PhishDestroy blocklist as a suspicious domain. Its name pairs the USDC stablecoin ticker with a number, which tends to draw in people looking for USDC-related services. PhishDestroy first flagged it on 2026-10-09. The site is now dead: its hosting provider blocked the content, it has been offline since 2026-10-14, and it was still down at the last check on 2026-10-19.
The page carried the title "onkeyon", which names no known wallet, exchange or token project and says nothing about what the site offered. That bland title sits next to a domain name built around USDC, and we have not assigned a specific scheme. The main risk with crypto-named domains like this is that visitors are asked to connect a wallet, sign transactions, or send stablecoins to an address they cannot verify. Any of those steps can cost the user funds that cannot be recovered.
Independent detection is thin. On 2026-10-13, VirusTotal showed 1 of 92 engines flagging the domain, with LevelBlue the only vendor. PhishDestroy is the only blocklist listing it. The domain appears in 4 AlienVault OTX pulses, which means other researchers have tracked it as part of threat activity. The provider's decision to block the content is the strongest outside sign that something on the site was a problem.
The domain was registered on 2025-11-09 through Gname.com Pte. Ltd. PhishDestroy flagged it about eleven months later, so it was either kept in reserve or ran unnoticed for most of that time. Traffic passed through Cloudflare, Inc. on an address geolocated to Canada. That setup hides the real origin server, which is why the block at the provider level is what took the site offline.
If you connected a wallet to usdc556.com, check its token approvals with a revocation tool, cancel anything you do not recognise, and move your funds if you signed anything unusual. If you sent USDC or other assets there, write down the transaction hashes and report them to the exchange or issuer involved. If you entered a seed phrase, treat that wallet as compromised and move your assets to a new one immediately. Defenders should block the domain, watch for lookalike USDC-numbered domains, and add the OTX pulse indicators to their monitoring.
Edge-IP の評判はこのドメインに起因しません。
drake.ns.cloudflare.comsofia.ns.cloudflare.comLocation describes the IP network.
e2008d3dcff57324a94756da7231b6262bce5df0536e8090b2c2a24b62cb28b0Saved 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.usdc556.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of usdc556.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
usdc556.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
不明→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
到達可能
1/92 engine detections
View sourceNo threat flag
View source4 community references
View sourcePD-20261009-C54688
usdc556.com
View sourcePage captured
View sourcePD-20261009-C54688 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 ↗
usdc556.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.