The Cyber Exposure Score is a published 0–100 formula built only from publicly observable signals. How this is calculated.
Posture summary
Email authentication
SPF ✓ -all DMARC quarantine DKIM ✓ · Microsoft 365 DNSSEC ✗ 9/10 SPF lookupsDNS hygiene
2 nameservers single DNS provider CAA ✗ IPv6 ✓Web & transport hygiene
HTTPS redirect ✗ HSTS ✓ CSP weak security.txt ✗TLS / certificate
TLS TLSv1.3 63d to expiryInternet exposure
2 open ports 0 KEVBreach metadata
0 public breaches on rhysida leak siteDomain & hosting
12 public hostnames AS42160 · LCPDCO LCP AS dc oostkamp no blocklist hitsAlso analysed: www.machelen.be
machelen.be sends visitors to www.machelen.be. Same registered domain, so the mail, DNS, lookalike and breach findings above apply to it unchanged; these are its own website checks.
score 86/100 · fair TLS TLSv1.3 59d to expiry HTTPS redirect ✓ HSTS ✓ CSP weak 2 open ports 0 KEVRansomware 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.
| Group | Listed | Sector |
|---|---|---|
| rhysida | 2026-10-27 | — |
Leak-site postings are collected here from 2026-07-30 onwards; an earlier listing would not appear above.
Source: Ransomware.live
Public attack surface (12 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.
The hostname inventory — which forgotten hosts exist and where — is part of the complete audit for this domain.
Recommendations
-
mediumEnable DNSSEC
DNSSEC signing was not detected for this domain.
-
criticalTreat data published on a leak site as disclosed
This domain is named on rhysida's public leak site on 2026-10-27. 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.
Sources: Ransomware.live · Have I Been Pwned (CC BY 4.0) · Shodan InternetDB
Refresh this report
Re-run a live analysis or generate a full downloadable audit.
Open live reportAll information is aggregated from public sources for awareness only and does not constitute an accusation or a security assessment. No personal data or credentials are published.