niclibya.com

The Cyber Exposure Score is a published 0–100 formula built only from publicly observable signals. How this is calculated.

Posture summary

Ransomware leak-site listings (1)

This domain is named on the public leak site of a ransomware group. A leak-site post is a claim published by the group — not a verified fact, and not a statement by this organization. Groups list victims who did not pay, overstate what they hold, and occasionally name the wrong company. What is certain is that the listing itself is public.

Leak-site postings are collected here from 2026-07-30 onwards; an earlier listing would not appear above.

Source: Ransomware.live

Public attack surface (27 hostnames in Certificate Transparency)

Hostnames this organization published in public TLS certificates. Passive OSINT — nothing was scanned; a wildcard certificate is in use, so the real footprint may be larger.

From the names alone: 0 remote access or sign-in, 1 admin tools, 2 non-production.

The hostname inventory — which forgotten hosts exist and where — is part of the complete audit for this domain.

Lookalike domains (1 registered of 102 checked)

Registered permutations of this domain. Existence is a fact, not an accusation — ownership and intent are not assessed. Those able to receive mail are the ones usable for invoice fraud and phishing. The Risk score (0–100) is a published formula weighing mail capability, registration age, spelling, what the homepage shows and phishing-feed hits, reduced when a name looks brand-owned (same registrar/nameservers, a redirect to this domain) or merely parked. How this is calculated.

Recommendations

• highEnforce DMARC

  No enforcing DMARC policy was observed. Publish a DMARC record and move to p=quarantine then p=reject to reduce spoofing.

• mediumEnable DNSSEC

  DNSSEC signing was not detected for this domain.

• criticalTreat data published on a leak site as disclosed

  This domain is named on krybit's public leak site on 2026-11-09. A leak-site post is a claim published by the group, not a verified fact — but the post itself is public, and if it is accurate the data is already out. Confirm the claim, then work from the assumption of disclosure: rotate every credential that touched the affected systems, invalidate active sessions, and check your notification duties under GDPR Art. 33/34.

• highReset credentials seen in infostealer logs

  Public infostealer telemetry associates 1 employee credential set(s) with this domain — passwords captured from infected devices, which bypass password policy and often session-hijack past MFA. Force a reset for the affected services, invalidate active sessions, and check the devices themselves.

• mediumLookalike domains are registered

  1 permutation(s) of this domain are registered. None accept mail today, but that can change without notice.

• mediumReview the public subdomain footprint

  27 hostnames for this domain appear in public Certificate Transparency logs. Retire forgotten hosts — stale subdomains are a common entry point and a takeover risk.