The Cyber Exposure Score is a published 0–100 formula built only from publicly observable signals. How this is calculated.
This domain scores better than 28% of the 330 Professional Services organisations we track (cohort median 79). The sample is seeded from public incident data, not a random cross-section of the sector.
Posture summary
Email authentication
SPF ✓ ~all DMARC ✗ DKIM ✗ DNSSEC ✗DNS hygiene
2 nameservers · OVH single DNS provider CAA ✗ IPv6 ✓Web & transport hygiene
HTTPS redirect ✓ HSTS ✗ CSP ✗ server version disclosed security.txt ✗TLS / certificate
TLS TLSv1.3 62d to expiryInternet exposure
2 open ports 0 KEV 3 version matchesBreach metadata
0 public breaches on krybit leak siteDomain & hosting
1 public hostnames registered 2008 AS16276 · OVH no blocklist hitsAlso analysed: www.ernat-bureau-etudes.fr
ernat-bureau-etudes.fr sends visitors to www.ernat-bureau-etudes.fr. Same registered domain, so the mail, DNS, lookalike and breach findings above apply to it unchanged; these are its own website checks.
score 75/100 · fair TLS TLSv1.3 63d to expiry HTTPS redirect ✓ HSTS ✗ CSP ✗ 2 open ports 0 KEVSoftware versions inside a published affected range (3, 3 known-exploited)
The public response carried a version for these products, and NVD publishes an affected range that contains it. This is not proof the software is unpatched — a distribution backport keeps the original version string while carrying the fix, so a fully patched build can appear here. Both halves of the comparison are public and checkable.
| CVE | Detected | Published affected range |
|---|---|---|
| CVE-2026-109618 KEV | PHP 8.2 | >= 7.3.0 and < 8.2.35 |
| CVE-2026-109619 KEV | PHP 8.2 | >= 5.4.0 and < 8.2.35 |
1 further match(es), with the affected range published for each, are part of the complete audit.
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.
| Group | Listed | Sector |
|---|---|---|
| krybit | 2026-08-07 | Professional Services |
Leak-site postings are collected here from 2026-07-30 onwards; an earlier listing would not appear above.
Source: Ransomware.live
Public attack surface (1 hostnames in Certificate Transparency)
Hostnames this organization published in public TLS certificates. Passive OSINT — nothing was scanned.
The hostname inventory — which forgotten hosts exist and where — is part of the complete audit for this domain.
Hosting footprint (1 of 1 known hostnames resolve)
Where this organisation's hostnames seen in Certificate Transparency actually point. A concentration in one provider is a resilience consideration, not a fault.
Providers
OVH · 1 IPv6 0%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 DKIM
No DKIM record was found on common selectors. Enable DKIM signing.
-
mediumEnable DNSSEC
DNSSEC signing was not detected for this domain.
-
criticalConfirm software versions that fall inside a published affected range
The public response carried a version for 2 detected product(s), and 3 published CVE ranges contain what we read. PHP 8.2 falls inside the range published as affected by CVE-2026-109618 (>= 7.3.0 and < 8.2.35). 3 are on CISA's known-exploited list, meaning exploitation has been observed in the wild. This is an observation about a version string, not proof the software is unpatched: a distribution backport keeps the original version while carrying the fix. Check the build you are actually running, and patch or upgrade whatever is genuinely inside the range.
-
criticalTreat data published on a leak site as disclosed
This domain is named on krybit's public leak site on 2026-08-07. 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 · CISA KEV catalog · NVD · FIRST EPSS · CVSS-BT
This product uses the NVD API but is not endorsed or certified by the NVD.
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.