Skip to content

Hostname

bakadata.com

Last fetched

bakadata.com resolves to 104.21.15.13, announced in 104.21.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. bakadata.com is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:49:47 GMT
Last seen on a feed
Tue, 22 Sep 2026 23:26:40 GMT

Nutrition Label

WHISPER CANON · bakadata.comRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/bakadata.com

Resolution chain

IPv6 resolution

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
gannerie lea
Contact emails
1o5icfnhj8j4qaa9g20g31annu@domaindiscreet.com, 468ace0d61764fb793172236c6b51247.protect@withheldforprivacy.com, 801f62cb4f894a4397bf24649c61fa4f.protect@withheldforprivacy.com, b7624d339b2d4359b26a52ef9b35654a.protect@withheldforprivacy.com, xgfdj0xpa6v3mw4msiap@g.o-w-o.info

Subdomains

Subdomain
m.bakadata.com
www.bakadata.com

Showing 2 of 4. View all subdomains →

Web-graph footprint

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

Sample inbound links

Mail and authentication

Nameservers

  • buck.ns.cloudflare.com
  • keyla.ns.cloudflare.com
  • 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
  • launch1.spaceship.net
  • launch2.spaceship.net

Threat-feed evidence

History

Related pages

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