Skip to security report
Analytics Dashboard
Domain security and threat intelligence
0.cc favicon

0.cc

In short

0.cc is a blocklisted domain detected by PhishDestroy on 2026-07-27. Risk: high (61/100). Registrar: eName Technology. Status: Content unavailable. VirusTotal: 2/89 engines flag it. Do not enter credentials or connect a wallet.

Registrar
eName Technology
Registered
Feb 17, 2007
PhishDestroy assessment High
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
Risk signals
VirusTotal detections: 2/89
OTX: 2 refs Jul 27, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
2 / 89
engine detections
Google Safe Browsing
No threat flag
OTX
2
community references
Domain age
7187 days
Source evidenceVirusTotal 2 / 89 · OTX 2 references 4 sources

VirusTotal

2 / 89 engine detections

Open report

OTX

2 community references

Open report

Google Safe Browsing

No threat flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

High
VirusTotal
2 / 89
OTX
2 community refs
Source results Registration record

PhishDestroy threat report

Overview

0.cc is a very short, single-character domain that PhishDestroy added to its blocklist after first detecting it on 2026-07-27. No impersonated brand or specific scheme has been confirmed, so it is listed as suspicious rather than tied to a named scam. The site has been dead since 2026-09-13 and was still unreachable when last checked on 2026-10-19.

How the scam works

Without a confirmed page or brand, the exact lure behind 0.cc cannot be described. What the evidence does show is a domain flagged by web-security vendors and threat-intelligence feeds, which usually points to content that leads visitors toward phishing, credential capture or malicious downloads. Short, memorable domains like this are valuable for redirect chains and shortened links, where a victim may land without ever typing the address.

Evidence

On 2026-09-13, VirusTotal showed 2 of 89 engines flagging the domain: Forcepoint ThreatSeeker and SOCRadar. That is a low count, but both are vendors that classify web threats and track external attack surface, so their verdicts carry weight. The domain also appears in two AlienVault OTX pulses, meaning other researchers have linked it to tracked malicious activity, and it is on the PhishDestroy blocklist.

Infrastructure

The domain went offline on 2026-09-13, about seven weeks after PhishDestroy first saw it. That is the same day it was checked on VirusTotal. A short active life followed by abrupt disappearance is a common pattern for disposable malicious domains, though it can also mean the operator simply abandoned it.

What to do

If you visited 0.cc and typed a password, change it everywhere you reuse it and turn on two-factor authentication. If you entered a wallet recovery phrase or private key anywhere you reached through this domain, treat that wallet as compromised and move your funds to a new one. If you downloaded anything, run a malware scan. Defenders should keep the domain blocked at DNS and proxy level, review logs for traffic between 2026-07-27 and 2026-09-13, and watch for the domain coming back online.

Useful links

VirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Cloudflare Radar · 2026-09-12T22:31:25Z

Observed: · Retrieved:

Uuid
e173b3a5-e802-4097-bce2-d2f7c44e3534
VirusTotal · 2026-10-13T15:39:39Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 4,
    "suspicious": 1,
    "undetected": 34
}
Vendor labels
{
    "CRDF": "malicious",
    "SOCRadar": "phishing",
    "Gridinsoft": "suspicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
eName Technology Co., Ltd.
Created
2007-02-17T05:14:43Z
Expires
2031-02-17T05:14:43Z
Updated
2026-08-10T07:05:07Z
First seen
2023-10-19T11:05:36Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1.ename.net"
    },
    {
        "ttl": 600,
        "type": "SOA",
        "rname": "admin.ename.net",
        "value": "ns1.ename.net"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns2.ename.net"
    }
]
Dns at
2026-10-13T16:09:53Z
Registration record
{
    "registrar": "eName Technology Co., Ltd.",
    "registrar_iana_id": "1331",
    "registrar_url": "http://www.ename.net",
    "created": "2007-02-17T05:14:43Z",
    "updated": "2025-12-30T11:47:08Z",
    "expires": "2031-02-17T05:14:43Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ns1.ename.net",
        "ns2.ename.net"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client delete prohibited",
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2031-02-17T05:14:43Z",
        "registration": "2007-02-17T05:14:43Z",
        "registrar expiration": "2031-02-17T05:14:43Z",
        "last update of RDAP database": "2026-08-10T07:05:07Z"
    }
}

Questions about 0.cc

Is 0.cc legit?

No. PhishDestroy classifies 0.cc as a blocklisted domain (risk: high, 61/100); it was first detected on 2026-07-27. VirusTotal: 2/89 engines flag it. Treat the site as unsafe.

Is 0.cc safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on 0.cc. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used 0.cc?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Domain details

Domain
OTX tags 2026-07all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar eName Technology SE(SE)
Abuse contact["abuse@ename.com", "d62c00d379702175s@gmail.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for 0.cc →
RegistrationCreated Feb 17, 2007 — Expires Feb 17, 2031
Time to First Unavailability 48 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedJul 27, 2026
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Nameservers 2

  • ns1.ename.net
  • ns2.ename.net
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

2 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 1 detection
Forcepoint ThreatSeeker
SOCRadar
Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

0.cc
Saved result
Unreachable
Stored observation history3

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unavailable→Reachable

  2. Availability monitor · Recorded state

    Reachable→Unavailable

  3. VirusTotal · Detection count

    1→2

Recorded activity

4 entries
  1. AlienVault OTX

    2 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    2/89 engine detections

    View source
  4. Added to PhishDestroy

    0.cc

    View source

Community intelligence

1 community report

CategoryOTHER_HACK

I am the victim of an unauthorized USDC transfer on Arbitrum One. On July 22, 2026 at 07:53:30 UTC, 101.060458 USDC was transferred from my wallet without my knowledge or intentional authorization. Victim address: 0x80717fe56db0f99917c888275fd83dc9d2f40156 Initial suspe

Evidence & External Reports

Security Analysis
VirusTotal 2 det. ChainPatrol ChainAbuse 1 report URLQuery SSL Labs CF Radar Open report OTX 2 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Community Scam Report — ChainAbuse
1 report filed for 0.cc (1 written by a person) · category: Other Hack · source checked
“I am the victim of an unauthorized USDC transfer on Arbitrum One. On July 22, 2026 at 07:53:30 UTC, 101.060458 USDC was transferred from my wallet without my knowledge or intentional authorization. Victim address: 0x80717fe56db0f99917c888275fd83dc9d2f40156 Initial suspected recipient: 0xb20523c91422814f59251927589698b852e105c2 Unauthorized transaction: 0xd17ed3541260b681d0452dc22ecfaffe01f6f846a0945fbe8f61a5da1f70b954 Transaction record: https://arbiscan.io/tx/0xd17ed3541260b6”
— reported by Anonymous on Jul 25, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

2 evidence signal groups linked 0 stored notification records Content unavailable

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including 0.cc)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
About this reportSources, observation dates and corrections

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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/0.cc"
  title="PhishDestroy threat report for 0.cc"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>