amzur.com

This domain scores better than 21% 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

Software versions inside a published affected range (3, 3 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.

1 further match(es), with the affected range published for each, are part of the complete audit.

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 (17 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 (12 registered of 77 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.

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.

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

• mediumEnable DNSSEC

  DNSSEC signing was not detected for this domain.

• criticalPatch known-exploited vulnerabilities

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

• criticalPatch what already has a public exploit

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

• criticalConfirm software versions that fall inside a published affected range

  The public response carried a version for 3 detected product(s), and 3 published CVE ranges contain what we read. Apache HTTP Server 2.4.41 falls inside the range published as affected by CVE-2021-40438 (<= 2.4.48). 3 are 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 unsafe's public leak site on 2026-08-28. 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.

• criticalNewly registered lookalike domains

  1 lookalike domain(s) were registered in the last 90 days, 1 of them able to receive mail: amzue.com (63d). 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

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