Posture summary
Email authentication
SPF ✓ DMARC reject DKIM ✗ DNSSEC ✗TLS / certificate
No valid TLSInternet exposure
6 open ports 4 KEVBreach metadata
0 public breaches on direwolf leak siteDomain & hosting
24 public hostnames registered 1998 AS4800 · LINTASARTA-AS-AP - PT Aplikanusa Lintasarta 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 |
|---|---|---|
| direwolf | 2026-09-01 | Manufacturing |
Leak-site postings are collected here from 2026-07-30 onwards; an earlier listing would not appear above.
Public attack surface (24 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
-
mediumEnable DKIM
No DKIM record was found on common selectors. Enable DKIM signing.
-
mediumEnable DNSSEC
DNSSEC signing was not detected for this domain.
-
highEnable valid HTTPS
No valid TLS was observed on port 443.
-
criticalPatch known-exploited vulnerabilities
4 known-exploited vulnerability(ies) may affect exposed services. Prioritize patching.
-
criticalPatch what already has a public exploit
4 vulnerability(ies) reported on this host have working exploit code published (Exploit-DB, Metasploit, Nuclei or a public PoC). Exploitation needs no development effort — patch these first.
-
criticalTreat data published on a leak site as disclosed
This domain is named on direwolf's public leak site on 2026-09-01. 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.
-
criticalReset credentials seen in infostealer logs
Public infostealer telemetry associates 9 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.
-
highGet a full security audit
Multiple exposures were detected. A professional audit can prioritize remediation.
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.