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 49% of the 209 Retail organisations we track (cohort median 78). The sample is seeded from public incident data, not a random cross-section of the sector.
Trend: Exposure up 14 since 2026-10-19 (7 days).
Posture summary
Email authentication
SPF ✓ ~all DMARC none DKIM ✓ DNSSEC ✗DNS hygiene
2 nameservers single DNS provider CAA ✗ IPv6 ✗Web & transport hygiene
HTTPS redirect ✓ HSTS ✗ CSP ✗ security.txt ✗TLS / certificate
TLS TLSv1.3 42d to expiryInternet exposure
13 open ports 0 KEVBreach metadata
0 public breaches on Deadlock leak siteDomain & hosting
0 public hostnames AS24940 · HETZNER-AS no blocklist hitsAlso analysed: www.rogdianakis.gr
rogdianakis.gr sends visitors to www.rogdianakis.gr. Same registered domain, so the mail, DNS, lookalike and breach findings above apply to it unchanged; these are its own website checks.
score 78/100 · fair TLS TLSv1.3 42d to expiry HTTPS redirect ✓ HSTS ✗ CSP ✗ 13 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 |
|---|---|---|
| Deadlock | 2026-10-02 | Other |
Leak-site postings are collected here from 2026-07-30 onwards; an earlier listing would not appear above.
Source: Ransomware.live
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 Deadlock's public leak site on 2026-10-02. 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.