hofbrauhaus-freising.de

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 57% of the 92 Agriculture and Food Production organisations we track (cohort median 78). The sample is seeded from public incident data, not a random cross-section of the sector.

Posture summary

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.

Leak-site postings are collected here from 2026-07-30 onwards; an earlier listing would not appear above.

Source: Ransomware.live

Public attack surface (11 hostnames in Certificate Transparency)

Hostnames this organization published in public TLS certificates. Passive OSINT — nothing was scanned.

From the names alone: 1 remote access or sign-in, 0 admin tools, 0 non-production.

The hostname inventory — which forgotten hosts exist and where — is part of the complete audit for this domain.

Lookalike domains (1 registered of 150 checked, 1 serving no website)

Registered permutations of this domain. Existence is a fact, not an accusation — ownership and intent are not assessed. Those able to receive mail are the ones usable for invoice fraud and phishing. The Risk score (0–100) is a published formula weighing mail capability, registration age, spelling, what the homepage shows and phishing-feed hits, reduced when a name looks brand-owned (same registrar/nameservers, a redirect to this domain) or merely parked. How this is calculated.

Recommendations

• criticalTreat data published on a leak site as disclosed

  This domain is named on lamashtu's public leak site on 2026-10-22. 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.

• highEnforce DMARC

  No enforcing DMARC policy was observed. Publish a DMARC record and move to p=quarantine then p=reject to reduce spoofing.

• highCheck the risky services Shodan reports open (to be checked)

  Shodan's last scan of this domain's address found 2 service port(s) that should not face the internet, such as remote desktop, databases or file sharing. We never connect to them, so this is not confirmed and not scored. Check from outside your network whether they answer; if they do, restrict them behind a firewall or VPN.

• highMonitor lookalike domains

  1 registered lookalike domain(s) can receive mail, which is what makes them usable for invoice fraud and credential phishing. 1 of those serves no website at all but can already receive mail, so a reply sent to it would be delivered although nothing is visible in a browser. With no website there is nothing to inspect, so watch for DNS or web changes rather than treating it as harmless. Monitor them and consider defensive registrations.

• mediumEnable DNSSEC

  DNSSEC signing was not detected for this domain.