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
0
threat pulses mention the domain
Online · HTTP 200
Cloudflare · 188.114.97.1 · TLS: Google Trust Services
Each check shows its own collection time. Zero detections do not guarantee safety.
Peniruan Google: usdc660.com — Dapat dijangkau · akses dibatasi (HTTP 403). Ringkasan bukti: VirusTotal 1/92 (Forcepoint ThreatSeeker); PhishDestroy score…
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
1 / 92 engine detections
Buka laporanScan report
Buka laporan3 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
usdc660.com is an impersonation phishing site whose name borrows the USDC stablecoin brand, a pattern aimed at crypto holders who trust anything that looks like an official USDC service. PhishDestroy first flagged it on 2026-10-09. The site has been offline since 2026-10-14, with its content blocked at the provider level, and it was still dead when rechecked on 2026-10-19.
Domains that pair a stablecoin name with a number usually front fake USDC earning, staking or deposit platforms. They present themselves as legitimate services and push visitors to send funds, connect a wallet or type in login details and recovery phrases. Whatever is handed over goes straight to the operators, and stolen stablecoins are rarely recoverable. The page itself carried the title "onkeyon", which does not reference USDC, while we classified the site as USDC impersonation.
Detection by outside engines is thin. On 2026-10-13, VirusTotal showed only 1 of 92 engines flagging the domain, Forcepoint ThreatSeeker. Beyond PhishDestroy's own blocklist, the domain appears in 3 AlienVault OTX threat pulses, which shows other researchers had already linked it to malicious activity. With most scanners silent, a clean result from a single engine should not be read as proof the site was safe.
The domain was registered on 2025-11-09 through Gname.com Pte. Ltd., almost eleven months before PhishDestroy caught it. A gap that long suggests the name was held in reserve or used quietly before this campaign surfaced. Traffic ran through Cloudflare, Inc., so the Canadian IP location belongs to Cloudflare's network and not to the operators' real server. The Google Trust Services certificate is the standard one issued for sites behind Cloudflare, so the padlock says nothing about whether the site could be trusted.
If you sent USDC or other funds to this site, stop all further payments, including any "unlock" or "withdrawal" fees, and report the transaction hashes to your exchange and to the police. If you connected a wallet, revoke the token approvals it granted. If you entered a recovery phrase, move your assets to a new wallet right away. Change any password you used there and turn on two-factor authentication. Security teams should block the domain and watch for sibling names that follow the same USDC-plus-number pattern.
Reputasi Edge-IP tidak dikaitkan dengan domain ini.
drake.ns.cloudflare.comsofia.ns.cloudflare.comLocation describes the IP network.
cef05888acb1709e188fe30256f93c2c19d23978d4c9ba3a1447ad26cdc426cfSaved 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.usdc660.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of usdc660.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
usdc660.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
Tidak diketahui→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
No threat flag
View source1/92 engine detections
View source3 community references
View sourcePD-20261009-4A51DA
usdc660.com
View sourcePage captured
View sourcePD-20261009-4A51DA 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 ↗
usdc660.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.