gibsonhospital.org

This domain scores better than 37% of the 217 Healthcare 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 (4 hostnames in Certificate Transparency)

Hostnames this organization published in public TLS certificates. Passive OSINT — nothing was scanned; a wildcard certificate is in use, so the real footprint may be larger.

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 and phishing-feed hits, reduced when a name looks brand-owned (same registrar/nameservers) or merely parked.

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 Wallstreet's public leak site on 2026-09-29. 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.

• 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.