Skip to content

Hostname

bksshoes.com

Last fetched

bksshoes.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. bksshoes.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · bksshoes.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/bksshoes.com

Resolution chain

No IPv4 resolution is recorded for bksshoes.com in WhisperGraph.

IPv6 resolution

No AAAA record for bksshoes.com is recorded in WhisperGraph.

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of bksshoes.com owner
Contact emails
nmorales@novushoes.com, 9c2d9f18-b6c8-43aa-8e88-580a40e358d5@identity-protect.org, a2810bae-4d67-467d-aa69-8b7331d4e433@identity-protect.org, b80308eb-6651-4729-9464-b960979f9d91@identity-protect.org, fe58c5a6-870f-487c-bb3e-0d3362de87e7@identity-protect.org

Subdomains

Showing 2 of 2 subdomains (2 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns-159.awsdns-19.com
  • ns-603.awsdns-11.net
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net
  • ns-1397.awsdns-46.org
  • ns-1604.awsdns-08.co.uk

MX records

  • bksshoes-com.mail.protection.outlook.com

SPF policy

  • include: spf.mandrillapp.com
  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

Pivot from bksshoes.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "bksshoes.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.