Skip to content

Hostname

bambuser.io

Last fetched

bambuser.io resolves to 13.227.192.107, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. bambuser.io 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 · bambuser.ioRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.3/10canon.whisper.security/host/bambuser.io

Resolution chain

IPv6 resolution

No AAAA record for bambuser.io is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:470
Registrant organisation
bambuser ab

Subdomains

Subdomain
1pass-scim.bambuser.io
eu-west-1-archive.bambuser.io
eu-west-1-s3archive.bambuser.io
legacy-ingest.bambuser.io
p.bambuser.io
poc.bambuser.io
preview.bambuser.io
telemetry.bambuser.io
us-east-1-archive.bambuser.io
us-west-2-archive.bambuser.io
us-west-2-s3archive.bambuser.io
wazuh.bambuser.io

Showing 12 of 12 subdomains (12 per page).

Mail and authentication

Nameservers

  • ns-129.awsdns-16.com
  • ns-640.awsdns-16.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-1079.awsdns-06.org
  • ns-1769.awsdns-29.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

Threat-feed evidence

History

Related pages

Pivot from bambuser.io 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: "bambuser.io"})-[: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.