This domain scores better than 33% of the 290 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 single DNS provider CAA ✗ IPv6 ✗Web & transport hygiene
HTTPS redirect ✓ HSTS ✗ CSP ✓ server version disclosed security.txt ✗TLS / certificate
TLS TLSv1.3 40d to expiryInternet exposure
0 open ports 0 KEVBreach metadata
0 public breaches on thegentlemen leak siteDomain & hosting
1 public hostnames registered 2022 AS47583 · AS-HOSTINGER Hostinger International Limited no blocklist hitsRansomware 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 |
|---|---|---|
| thegentlemen | 2026-09-30 | 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.
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.
-
criticalTreat data published on a leak site as disclosed
This domain is named on thegentlemen's public leak site on 2026-09-30. 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.