fanatics.com

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 (219 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 (46 registered of 104 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.

43 further registered lookalike(s), 31 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 N0n's public leak site on 2026-09-20. 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 1 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 1970-01-01. Most commonly RedLine. Force a reset for the affected services, invalidate active sessions, and check the devices themselves.

• mediumReview third-party credential exposure

  65 credential set(s) for third-party services used by this domain appear in the same telemetry. Supplier and SaaS accounts are a common lateral path.

• criticalNewly registered lookalike domains

  1 lookalike domain(s) were registered in the last 90 days, 1 of them able to receive mail: fanaticssupport.com (61d). A registration this recent is the strongest public signal of intent there is — brand-new names are what invoice fraud and credential phishing are staged from, and they are usually registered days before they are used. Ownership and intent are not assessed here; the registration date is a registry fact. Report any that impersonate you to the registrar, warn finance and staff, and consider defensive registrations.

• highMonitor lookalike domains

  31 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 — registered, silent and already able to accept a reply. A name in that state is typically pointed at something only when it is about to be used, so it is worth watching before anything appears on it. Monitor them and consider defensive registrations.

• mediumReview the public subdomain footprint

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