VirusTotal
0 / 92
engines flag the domain
“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.
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 · 188.114.96.1 · TLS: Google Trust Services
Each check shows its own collection time. Zero detections do not guarantee safety.
Domain dalam daftar blokir: usdc226.com — Dapat dijangkau · akses dibatasi (HTTP 403). Ringkasan bukti: VirusTotal 2/92 (Forcepoint ThreatSeeker, LevelBlue)…
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
2 / 92 engine detections
Buka laporanScan report
Buka laporan4 community references
Buka laporanprovider verdict: clean
Buka laporanNo threat flag
Buka laporanNo malicious flag
Buka laporanResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
usdc226.com is on the PhishDestroy blocklist as a suspicious domain. Its name pairs the USDC stablecoin ticker with a number, the kind of label that catches the eye of people holding or trading stablecoins. PhishDestroy first flagged it on 2026-10-09. The site is now dead: the hosting provider has blocked its content, and it has been offline since 2026-10-14, which was confirmed again on 2026-10-19.
The page carried the title "onkeyon", which does not mention USDC or any crypto brand. The domain name itself still points at stablecoin users. A site that borrows a token's name without belonging to its issuer can lure visitors into connecting a wallet, sending funds or typing in sensitive details, and any of those can lead to losses. The site has no confirmed scheme type, so treat any USDC-themed offer or prompt you saw there as untrusted.
Independent detection is thin. On 2026-10-13, 2 of 92 VirusTotal engines flagged the domain: Forcepoint ThreatSeeker and LevelBlue. The domain also appears in 4 AlienVault OTX threat pulses, so other researchers have tracked it as well. Outside PhishDestroy, no blocklist carries it. The provider's decision to block the content adds weight, but the case rests on limited signals.
The domain was registered on 2025-11-09 through Gname.com Pte. Ltd., about eleven months before PhishDestroy detected it. A domain that sits that long before use may have been held in reserve or used quietly before anyone noticed. Traffic ran through Cloudflare, with the address resolving to Canada, so the real origin server stays hidden behind the network. Its certificate came from Google Trust Services, the standard issuer for Cloudflare-fronted sites, so the browser padlock said nothing about whether the site was legitimate.
If you connected a wallet to usdc226.com, use a token-approval checker to review the approvals it granted and revoke any you do not recognize. Then move your remaining assets if you signed anything unusual. If you entered a seed phrase or private key, consider that wallet compromised and move your funds to a new one right away. If you only typed in a password or email, change that password and turn on two-factor authentication. Defenders should block the domain and look in their logs for earlier visits, since it was registered long before it was detected.
Reputasi Edge-IP tidak dikaitkan dengan domain ini.
drake.ns.cloudflare.comsofia.ns.cloudflare.comLocation describes the IP network.
ff56927d653a37ad4b4273932ef585696f4084e116e06952604dc6e07ce5ba16Saved 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.usdc226.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of usdc226.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
usdc226.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Tidak diketahui→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Tidak diketahui→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Tidak diketahui→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
live_content→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Dapat dijangkau→Tidak tersedia
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Dapat dijangkau
2/92 engine detections
View sourceNo threat flag
View source4 community references
View sourcePD-20261009-1265AA
usdc226.com
View sourcePage captured
View sourcePD-20261009-1265AA 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)
Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
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 ↗
usdc226.com)Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.
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
Analisis ancaman menggunakan daftar blokir yang disimpan, WHOIS, DNS, dan bukti pemindaian publik
Pindai SekarangLaporkan domain yang mencurigakan ke basis data ancaman kami — lindungi komunitas
LaporanLaporan phishing terbaru dan perubahan ketersediaan yang diamati
PantauPantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive
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.