c-o.space is a phishing page detected by PhishDestroy on 2026-10-08. Risk: critical (88/100). Registrar: Ledl.net. Status: Last known active. Hosting: Amazon.com, Inc. PhishDestroy sent 1 abuse report. VirusTotal: 6/92 engines flag it. Do not enter credentials or connect a wallet.
Security engines reporting a detection: 6. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@ledl.net.
The latest stored availability evidence still shows the domain reachable; 14 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.
c-o.space is a domain on the PhishDestroy blocklist. Its page title simply repeats the domain name, so it does not show which brand or service it imitates or whom it targets. PhishDestroy first flagged it on 2026-10-08, and as of 2026-10-19 the site was still online and serving live content.
How the scam works
PhishDestroy has not yet assigned this domain a specific scheme type, and the bare page title offers no brand or lure. The risk is that a flagged, still-live site in the crypto threat space can present a login form, a wallet-connect prompt or a request for a recovery phrase. Any credentials, signatures or seed words handed to such a page can give an attacker control of accounts or funds. Until a classification is published, treat any request for sensitive data on this domain as hostile.
Evidence
On 2026-10-08, VirusTotal showed 6 of 92 engines flagging the domain: alphaMountain.ai, BitDefender, Forcepoint ThreatSeeker, Fortinet, G-Data and Gridinsoft. That is a minority of engines, but six unrelated vendors agreeing is a meaningful signal. The domain also appears in 29 AlienVault OTX pulses, which means threat researchers have repeatedly tied it to reported malicious activity. PhishDestroy is the only blocklist listed for it.
Infrastructure
The domain was registered on 2025-07-29 through Ledl.net GmbH & Co KG, more than a year before PhishDestroy detected it. That long gap suggests an aged domain rather than a throwaway registered just before an attack. It is hosted on Amazon.com, Inc. infrastructure in the US, and the free Let's Encrypt certificate means the padlock in the browser says nothing about whether the site is trustworthy.
What to do
If you entered a password on c-o.space, change it everywhere you reuse it and turn on app-based two-factor authentication. If you typed a seed phrase or private key there, consider that wallet compromised and move any remaining assets to a newly created wallet right away. Do not return to the site to check whether it is still live. Defenders should block the domain at DNS and proxy level, search logs for visits since 2026-10-08, and use the OTX pulses to find related indicators.
No. PhishDestroy classifies c-o.space as a phishing page (risk: critical, 88/100); it was first detected on 2026-10-08. VirusTotal: 6/92 engines flag it. Treat the site as unsafe.
Is c-o.space safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on c-o.space. 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 c-o.space?
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.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
3.234.189.133
Network ASN
AS14618
Organization
AWS EC2 (us-east-1)
Observed location
Ashburn, US
Server header
Cargo
Nameservers 2
ns1.cargo.site
ns2.cargo.site
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YE2
Valid from
2026-10-07 23:21:12
Valid until
2027-01-05 23:21:11
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-11 10:02:21 UTC
Collection source
PhishDestroy collector
Certificate fingerprintdce836ec953e1f3a5fd130ea9207e8505ae05cb9c058dcadfc4200c3d3422079Certificate names · 1 SAN
c-o.space
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-10-22 10:37:31 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-22 10:37:31 UTClast content: 2026-10-22 10:37:31 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains2
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
mail.c-o.spaceDomain record
www.c-o.spaceDomain record
The original observation time is not recorded for these hostnames.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · c-o.space
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
PDF notice generated Notice text archived (594 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (DE):
German Criminal Code § 263 (Fraud)
German Criminal Code § 263a (Computer Fraud)
Telemedia Act (TMG)
German law prohibits fraud and computer-based deception.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
6 evidence signal groups linked1 stored notification recordsLast known active
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.
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 →
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 c-o.space)
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)
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
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.
(DE)
