Skip to content

Hostname

bksta.com

Last fetched

bksta.com resolves to 35.79.8.35, announced in 35.72.0.0/13 by AMAZON-02 - Amazon.com, Inc. in JP. bksta.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 · bksta.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/bksta.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of bksta.com owner
Contact emails
bc364bb7c3084814afed0036a62ef477.protect@whoisguard.com, 2b23b27c-9035-488a-9fe8-74cdec8a9c71@identity-protect.org, 5bf3a0f4-8f3b-4cf3-adbe-71b79518bf18@identity-protect.org, 9ff9f016-08b1-4b48-bc24-cf1caa97387c@identity-protect.org, b8d723c2-30b3-4dd5-9e04-7bb4c3ce35ee@identity-protect.org, dac80cd5-2515-49fd-832a-14a1cef1a72a@identity-protect.org, dbb522a9-884e-45da-b2e4-d07af5bbd6a3@identity-protect.org, owner-977562@bksta.com.whoisprivacyservice.org

Subdomains

Showing 3 of 3 subdomains (3 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-31.awsdns-03.com
  • ns-726.awsdns-26.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-1401.awsdns-47.org
  • ns-1603.awsdns-08.co.uk

MX records

  • inbound-smtp.us-east-1.amazonaws.com

Threat-feed evidence

History

Related pages

Pivot from bksta.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: "bksta.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.