Google Safe Browsing
No threat flag
Not on Google threat lists at check time
“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.
No threat flag
Not on Google threat lists at check time
0
threat pulses mention the domain
Online · HTTP 200
Cloudflare · 172.67.220.195 · TLS: Google Trust Services
Each check shows its own collection time. Zero detections do not guarantee safety.
Google taklidi: usdc059.com — Ulaşılabilir · erişim kısıtlı (HTTP 403). Kanıt özeti: VirusTotal 2/92 (Forcepoint ThreatSeeker, LevelBlue); URLQuery 2 det.; CF…
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
2 / 92 engine detections
Raporu aç2 det.
Raporu açZararlı
Raporu aç4 community references
Raporu açNo threat flag
Raporu açNo malicious flag
Raporu açResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
usdc059.com is an impersonation phishing site whose name borrows the USDC stablecoin brand, padded with a number so it looks like one of many official-sounding variants. It targets crypto users who hold or are looking for USDC. PhishDestroy first flagged it on 2026-10-09. The site has been offline since 2026-10-14, its content is blocked at the provider level, and it was still down when last checked on 2026-10-19.
Sites like this present themselves as a USDC service, such as a rewards claim, a staking or redemption portal, or a support page, to borrow the trust attached to a widely used stablecoin. The page carried only the generic title "Home," which shows no brand, while we classified the site as impersonation based on its overall setup. The usual goal is to get the visitor to send USDC or other tokens as a "deposit" or "fee," connect a wallet and sign a transaction that grants spending rights, or type in a recovery phrase. Any of these can leave the victim with an emptied wallet and no way to reverse the transfers.
On 2026-10-13, VirusTotal showed only 2 of 92 engines flagging the domain, Forcepoint ThreatSeeker and LevelBlue. That low count means most security tools would not have warned a visitor during the days the site was live. The domain also appears in 4 AlienVault OTX threat pulses, so other researchers had tied it to malicious activity independently. PhishDestroy is the blocklist carrying it.
The domain was registered on 2025-12-29 through Gname.com Pte. Ltd., roughly nine months before it was detected, which suggests it sat parked or quietly in use before the campaign surfaced. Traffic ran through Cloudflare's network with a Canadian location, so the address seen publicly is a proxy edge and not the real origin server. Its Google Trust Services certificate put a padlock in the browser, but that only means the connection was encrypted and says nothing about whether the site was legitimate.
If you sent USDC or other tokens to this site, record the transaction hashes and report them to the exchange or service that funded your wallet, and do not pay any further "unlock" or "verification" fees. If you connected a wallet and signed anything, revoke the token approvals granted during that session with a trusted approval checker. If you entered a recovery phrase, treat the wallet as compromised and move what remains to a newly created one immediately. Defenders should block the domain and other numbered USDC-themed lookalikes, and watch for the same operator returning on fresh registrations.
Edge-IP itibarı bu etki alanıyla ilişkilendirilmez.
drake.ns.cloudflare.comsofia.ns.cloudflare.comLocation describes the IP network.
9a766bfeea71436c428e9d24a7816aeed7cf12159103563c680ae0278a2c3af9Saved 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.usdc059.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of usdc059.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
usdc059.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Bilinmiyor→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Bilinmiyor→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Bilinmiyor→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
live_content→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Erişilebilir→Mevcut değil
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Erişilebilir
No threat flag
View source2/92 engine detections
View source4 community references
View sourcePD-20261009-0C1CDF
usdc059.com
View sourcePage captured
View sourcePD-20261009-0C1CDF 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)
Hesap kimlik bilgilerini, kişisel bilgileri veya ödeme bilgilerini girdiyseniz ya da bu alan adından bir dosya indirdiyseniz hemen harekete geçin. Aşağıda olayı bildirmenize ve kendinizi korumanıza yardımcı olacak kaynaklar bulunmaktadır.
resmi siber suç iletişim bilgileri veya şikayet taslağı oluştur → almak için ülkenizi seçin.
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 ↗
usdc059.com)Tüm ayrıntıları bilmeseniz bile — yine de şikayette bulun. Kısmi bilgiler de soruşturmalara yardımcı olmaktadır.
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
Saklanan engelleme listesi, WHOIS, DNS ve genel tarama kanıtlarını kullanarak tehdit analizi
Şimdi TaraŞüpheli alan adlarını tehdit veritabanımıza bildirin — topluluğu koruyun
BildirSon kimlik avı raporları ve gözlemlenen kullanılabilirlik değişiklikleri
İzleCanlı tehditleri izleyin veya bunun yanlış bir uyarı olduğunu düşünüyorsanız bu kayda itiraz edin
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.