manroc.com

The Cyber Exposure Score is a published 0–100 formula built only from publicly observable signals. How this is calculated.

We track 14 Real Estate organisations — too few to publish a percentile yet. The sample is seeded from public incident data, not a random cross-section of the sector.

Posture summary

Software versions inside a published affected range (1, 1 known-exploited)

The public response carried a version for these products, and NVD publishes an affected range that contains it. This is not proof the software is unpatched — a distribution backport keeps the original version string while carrying the fix, so a fully patched build can appear here. Both halves of the comparison are public and checkable.

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 (9 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.

Lookalike domains (18 registered of 86 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.

15 further registered lookalike(s), 8 of them able to receive mail. The full list, with mail capability for each, is part of the complete audit.

Recommendations

• highEnforce DMARC

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

• criticalConfirm software versions that fall inside a published affected range

  The public response carried a version for 3 detected product(s), and 1 published CVE range contains what we read. jQuery 1.11.0 falls inside the range published as affected by CVE-2020-11023 (>= 1.0.3 and < 3.5.0). 1 is on CISA's known-exploited list, meaning exploitation has been observed in the wild. This is an observation about a version string, not proof the software is unpatched: a distribution backport keeps the original version while carrying the fix. Check the build you are actually running, and patch or upgrade whatever is genuinely inside the range.

• criticalTreat data published on a leak site as disclosed

  This domain is named on Storm's public leak site on 2026-09-21. 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

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