sancity.in

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.

Lookalike domains (4 registered of 96 checked)

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.

1 further registered lookalike(s), 2 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.

• highPublish SPF

  No SPF record was observed. Publish one listing authorized senders.

• 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

  1 known-exploited vulnerability(ies) may affect exposed services. Prioritize patching.

• criticalPatch what already has a public exploit

  1 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 Vexy Ransomware's public leak site on 2026-09-06. 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

  2 registered lookalike domain(s) can receive mail, which is what makes them usable for invoice fraud and credential phishing. Monitor them and consider defensive registrations.

• highGet a full security audit

  Multiple exposures were detected. A professional audit can prioritize remediation.