Skip to content

Hostname

bambuserplus.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:470
Registrant organisation
bambuser ab
Contact emails
legal-se@rouse.com, bambuserplus.com-registrant@anonymised.email

Subdomains

Subdomain
creator-payments.bambuserplus.com
creator.bambuserplus.com
graph-staging.bambuserplus.com
graph.bambuserplus.com
hasura.bambuserplus.com
internal.bambuserplus.com
manager-staging.bambuserplus.com
manager.bambuserplus.com
metabase.bambuserplus.com
unsubscribe.bambuserplus.com
workspace.bambuserplus.com

Showing 11 of 11 subdomains (11 per page).

Mail and authentication

Nameservers

  • ns-118.awsdns-14.com
  • ns-688.awsdns-22.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-1232.awsdns-26.org
  • ns-1993.awsdns-57.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

SPF policy

  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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