Aller au rapport de sécurité
Sécurité des domaines et renseignements sur les menaces
olks.cx favicon

olks.cx

“OLinks”

Bureau d’enregistrement
CentralNic
Resolved IP
104.20.26.126
Registered
24/02/2026
PhishDestroy assessment Critique
Disponibilité Dernier actif connu Dernière observation d'accessibilité stockée Observé · HTTP probe
Détections VirusTotal : 1/92
OTX: 4 refs 19/10/2026 1 Report Sent CDN
API
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 1. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
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.

Elapsed since first report
29 hours
Reports sent
1
Latest case ID
PD-20261019-45B070
Current status
HTTP 200 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Résumé du rapport

Domaine sur listes de blocage: olks.cx — Dernier actif connu (HTTP 200). Résumé des preuves: VirusTotal 1/92 (SOCRadar); PhishDestroy score 81/100. Bureau…

L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.

Source evidenceVirusTotal 1 / 92 · OTX 4 references 6 sources

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

Analysis

Critique
VirusTotal
1 / 92
OTX
4 community refs
Page captures
1

PhishDestroy threat report

Overview

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.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Capture enregistrée · 1 capture

Domain details

Domaine
URLScan verdict Analyse terminée score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden La réputation Edge-IP n’est pas attribuée à ce domaine.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainesdrainerfraudlivemonthlyphishdestroyphishingscam
Bureau d’enregistrement CentralNic GB(GB)
EnregistrementCréé 24/02/2026 (238d) — Expires 24/02/2027
Statut HTTP200
Détails techniquesProvenance & timestamps
Première détection19/10/2026
DOM Analysisanalyzed 19/10/2026score 81/100
Submitted URLhttps://olks.cx/
Favicon Hash
ID du dossier
Observed page title
OLinks
Certificat TLS
Émis par Let's Encrypt / YE2 · stored validity ends in 41 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.20.26.126
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

La réputation Edge-IP n’est pas attribuée à ce domaine.

Serveurs de noms 2

  • donna.ns.cloudflare.com
  • sergi.ns.cloudflare.com

Location describes the IP network.

Certificat TLS

Issuer
Let's Encrypt / YE2
Valid from
2026-09-02 15:35:50
Valid until
2026-12-01 15:35:49
Validity
Within stored validity dates
Collection time
2026-10-19 13:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprinta6691f0f817d72d6216b9003eecd9bd1e0f86840d333d14ccfa8215de28e314d

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-19 23:02:59 UTC

Primary outcome Contenu actif reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Contenu actif Ordinary HTTP content served 90% 2026-10-19 23:02:59 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-19 23:02:59 UTC last 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
Detected via Cloudflare Radar · Wappalyzer engine
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Analyse VirusTotal

1 / Les fournisseurs de sécurité 92 ont signalé ce domaine
View on VT
Last analyzed First positive detection
SOCRadar

Preuves archivées

Wayback Machine Snapshot
Un instantané historique est disponible pour l’examen des preuves
View Archive
Analyse des performances du site

Google PageSpeed Insights — mobile performance audit of olks.cx · checked Oct 19, 2026

60
Needs Work
Performance
FCP
6.83s
First Contentful Paint
LCP
7.58s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
6.83s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: https://olks.cx/
OLinks
Réponse
HTTP 200
HTML body
1.0 KB
Compressed
425 B
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
Security headers present
X-Frame-OptionsX-Content-Type-OptionsX-XSS-ProtectionReferrer-PolicyPermissions-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: 3e9594ca9515d1e62338f414a5780d7203d573ca6bf3513bc6a67120bbfe7de0
Saved response-header values · 18
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a4cfd8709b609fc9-AMS
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Mon, 19 Oct 2026 12:39:25 GMT
Last-Modified
Fri, 14 Aug 2026 13:03:52 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
onion-location
http://olinksxbvtj6rm55yppju7i3wkz3pbhmzezow24gyxkqbpxdbgp435ad.onion/
Permissions-Policy
geolocation=(), microphone=(), camera=()
Referrer-Policy
strict-origin-when-cross-origin
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=g32hoPkpCsHDsmjxWyJEdhB%2BgqnyCLXhh1474Z5RRQTmI5nRybBwiBa3MR5k03IL8iruQysezNwft3hK2uZC%2BGPJ2TatqqyLZ%2BziM1DAcuqW2g8EQcPYalh%2F"}]}
Server
cloudflare
Transfer-Encoding
chunked
X-Content-Type-Options
nosniff
X-Frame-Options
DENY
X-XSS-Protection
1; mode=block

Values retained by the collector; long values may be shortened during collection.

Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Stored observation history2

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

    Inconnu→live_content

    content_served

  2. Availability monitor · First collection record

    Accessible

Recorded activity

6 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. AlienVault OTX

    4 community references

    View source
  3. VirusTotal

    1/92 engine detections

    View source
  4. Abuse report sent

    PD-20261019-45B070

    abuse@key-systems.net
  5. Added to PhishDestroy

    olks.cx

    View source
  6. URLScan

    Page captured

    View source

Check for cloaking

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

olks.cx

Données factuelles et rapports externes

Instantané des preuves transmises
Sent: Ledger records: 1 Case ID: PD-20261019-45B070 Recipient: abuse@key-systems.net
PDF notice generated
Référencement naturel et nom de domaine
Analyse approfondie
Help & reporting

Ce site vous a-t-il affecté ?

6 evidence signal groups linked 1 stored notification records Dernier actif connu
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.

Official reporting routes

Méfiez-vous des escrocs qui prétendent vous aider à récupérer vos biens ! Les criminels peuvent recontacter leurs victimes tout en se faisant passer pour des enquêteurs, des avocats ou des agents de recouvrement. Ne payez pas de frais initiaux et ne partagez pas vos informations d'identification. En savoir plus sur la fraude liée aux aides à la reprise →

Signalez-le à vos autorités locales

Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.

Annuaire de 97 pays

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

Brouillon assisté par l'IA : les détails de l'incident sont traités par le fournisseur d'IA · Examinez-le et soumettez-le vous-même
After a phishing incident

Recommandations et conseils à l'intention des victimes

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

Que dois-je faire tout de suite ?

Urgent

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

  • Modifier tous les mots de passe — e-mail, comptes Exchange, tout ce qui utilise le même mot de passe
  • Activer l'authentification à deux facteurs (2FA) en utilisant une application d'authentification (et non par SMS). Désactivez la récupération par SMS
  • Cartes « Freeze » si vous avez saisi vos coordonnées bancaires sur le site de hameçonnage

Quelles informations dois-je rassembler pour mon rapport ?

Directives du FBI

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.
  • Dates et horaires exacts — de chaque transaction et du premier contact avec l'escroc
  • Captures d'écran — sites web frauduleux, messages de chat, e-mails, transactions via des portefeuilles numériques, réseaux sociaux
  • Toutes les URL et tous les noms de domaine utilisés par l'escroc (notamment olks.cx)
  • Communications — les e-mails, SMS, numéros de téléphone et noms d'utilisateur utilisés par l'escroc

Même si vous ne disposez pas de tous les détails — déposer quand même une plainte. Même des informations partielles peuvent aider les enquêtes.

À qui dois-je signaler cette arnaque ?

  • FBI IC3 — Centre de signalement des délits sur Internet (système fédéral américain de signalement)
  • Europol — Rapports sur la cybercriminalité en Europe (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Police locale — permet de consigner officiellement la situation, même s’ils ne peuvent pas agir immédiatement

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?

  • Faux sites web — des clones identiques au pixel près de sites légitimes, dont les noms de domaine ont été légèrement modifiés
  • Découpe du porc — une relation de confiance établie au fil des semaines via Telegram, WhatsApp ou des applications de rencontre, puis une escroquerie financière
  • Arnaques liées au recouvrement — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Escroqueries basées sur l'IA — les « deepfakes », le hameçonnage automatisé et les sites générés par l'IA, qui rendent la fraude plus difficile à détecter

Comment puis-je me protéger à l'avenir ?

  • Ajouter les sites officiels à vos favoris — Ne cliquez jamais sur les liens contenus dans les e-mails, les messages privés ou les publicités
  • Vérifier les noms de domaine — vérifier si PhishDestroy avant d'entrer en contact. Vérifiez le protocole HTTPS, l'orthographe et l'ancienneté du domaine
  • « Trop beau pour être vrai » = arnaque — des rendements garantis, des témoignages de célébrités, des délais serrés

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

Restez informés, restez en sécurité

Surveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif

Flux d'alertes en temps réel Contester cette annonce
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Intégrer ce rapport

Partagez ces informations sur les menaces sur votre site web ou votre blog

embed.html
<iframe
  src="https://phishdestroy.io/fr/embed/domain/olks.cx"
  title="PhishDestroy threat report for olks.cx"
  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>