clover.com

This domain scores better than 87% of the 193 Retail 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 (567 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 (50 registered of 86 checked, 3 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.

1 of these were registered in the last 90 days, 1 of them able to receive mail. Recent registration is a risk indicator, not evidence of intent: many lookalikes are defensive registrations, unrelated businesses or parked inventory.

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

Recommendations

• mediumEnable DNSSEC

  DNSSEC signing was not detected for this domain.

• criticalTreat data published on a leak site as disclosed

  This domain is named on clop's public leak site on 2026-08-12. 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.

• highReset credentials seen in infostealer logs

  Public infostealer telemetry associates 2 employee credential set(s) with this domain — passwords captured from infected devices, which bypass password policy and often session-hijack past MFA. The most recent dates from 2024-12-24. Most commonly Generic Stealer. Force a reset for the affected services, invalidate active sessions, and check the devices themselves.

• mediumStrengthen password requirements

  50% of the exposed employee passwords analysed rate as weak or very weak. Raise minimum length and screen new passwords against breach lists.

• criticalNewly registered lookalike domains

  1 lookalike domain(s) were registered in the last 90 days, 1 of them able to receive mail: ckover.com (82d). Recent registration is one brand-risk indicator among several — with name similarity, mail capability and live web content — and together they describe what a name is able to do, not who registered it or why: many lookalikes are defensive registrations, unrelated businesses or parked inventory. The registration date is a registry fact; ownership and intent are not assessed. Check these against your own registrations, report any that impersonate you to the registrar, warn finance and staff about payment-change requests, and consider defensive registrations.

• highMonitor lookalike domains

  36 registered lookalike domain(s) can receive mail, which is what makes them usable for invoice fraud and credential phishing. 2 of those serve no website at all but can already receive mail, so a reply sent to them 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 them as harmless. Monitor them and consider defensive registrations.

• mediumReview the public subdomain footprint

  567 hostnames for this domain appear in public Certificate Transparency logs. Retire forgotten hosts — stale subdomains are a common entry point and a takeover risk.