Security engines reporting a detection: 1. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 24H+ 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@key-systems.net.
The latest stored availability evidence still shows the domain reachable; 29 hours 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.
olks.cx is a newly registered domain that currently shows no reachable web content. PhishDestroy added it to its blocklist on 2026-10-19 after the first sighting. The site is marked as alive but its content is unreachable as of the same date. The domain appears to be aimed at cryptocurrency users, although no specific brand is displayed.
How the scam works
The lack of visible pages suggests the domain is used as a landing point for phishing links or malicious redirects that harvest wallet credentials or private keys. Attackers typically lure victims with promises of crypto services, then capture login data or request wallet approvals. Once the information is collected, the adversary can empty the victim’s wallets or perform unauthorized transactions. The risk therefore centers on loss of crypto assets rather than traditional financial theft.
Evidence
VirusTotal scanned the domain and recorded one detection out of 92 engines, with SOCRadar flagging it as malicious. Open Threat Exchange lists four pulses that reference the same domain. PhishDestroy itself lists the domain on its blocklist. No additional detections from Google Safe Browsing, urlscan.io or Spamhaus are present in the current data.
Infrastructure
The domain was registered on 2026-02-24 through CentralNic Ltd, giving it roughly eight months of existence before being flagged. Hosting resolves to IP 104.20.26.126, a network commonly associated with a global CDN provider. The TLS certificate is issued by Let’s Encrypt under the identifier YE2, indicating a standard free SSL deployment. These elements point to a low‑cost, quickly provisioned operation rather than a long‑standing infrastructure.
What to do
Anyone who visited olks.cx should change all passwords used on crypto platforms, enable two‑factor authentication, and review recent transaction history for unauthorized activity. If a wallet address or private key was ever entered, move funds to a new wallet and revoke any token approvals granted to unknown contracts. Security teams should block the domain at the network perimeter, add it to internal threat feeds, and monitor DNS logs for other domains registered by the same registrar. Continuous monitoring for similar patterns can help prevent future exposure.
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-19 23:02:59 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-19 23:02:59 UTClast content: 2026-10-19 23:02:59 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.
Technologies · 2 identified
Cloudflare
CDN
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
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 olks.cx)
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.
(GB)
