bk.com

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

Posture summary

Public attack surface (38 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 (27 registered of 55 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, 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.

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

• mediumReview third-party credential exposure

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

• highMonitor lookalike domains

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

• mediumReview the public subdomain footprint

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