Hostname
bambora.com
Last fetched
bambora.com resolves to 4 IPv4 addresses operated by FASTLY - Fastly, Inc. in CA. WHOIS lists iana:638 as the registrar.
Nutrition Label
Resolution chain
bambora.com resolves to 4 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 151.101.131.10 | 151.101.128.0/22 | AS54113 | FASTLY - Fastly, Inc. | CA |
| 151.101.195.10 | 151.101.192.0/22 | AS54113 | FASTLY - Fastly, Inc. | CA |
| 151.101.3.10 | 151.101.0.0/22 | AS54113 | FASTLY - Fastly, Inc. | CA |
| 151.101.67.10 | 151.101.64.0/22 | AS54113 | FASTLY - Fastly, Inc. | CA |
WHOIS identity
- Registrar
- iana:638
- Organization
- bambora device ab
- Contact emails
Subdomains
36 observed subdomains of bambora.com.
Showing 25 of 36. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from bambora.com in the public web crawl.
624 sites link to this hostname.
Sample inbound links
Sample outbound links
Threat posture
History
Mail and authentication
SPF policy
26 SPF mechanisms authorising senders for bambora.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.salesforce.com |
| SPF_INCLUDE | amazonses.com |
| SPF_INCLUDE | mail.zendesk.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 107.6.3.144/28 |
| SPF_IP | 142.179.103.55/32 |
| SPF_IP | 149.72.23.30/32 |
| SPF_IP | 149.72.63.5/32 |
| SPF_IP | 168.245.198.40/29 |
| SPF_IP | 184.69.102.12/32 |
| SPF_IP | 199.243.79.232/29 |
| SPF_IP | 204.101.59.112/29 |
| SPF_IP | 217.115.65.11/32 |
| SPF_IP | 217.115.65.13/32 |
| SPF_IP | 217.115.65.14/32 |
| SPF_IP | 217.115.67.7/32 |
| SPF_IP | 217.115.67.8/32 |
| SPF_IP | 52.17.140.228 |
| SPF_IP | 52.49.166.191 |
| SPF_IP | 52.50.234.48 |
| SPF_IP | 64.251.76.244/32 |
| SPF_IP | 72.2.4.128/32 |
| SPF_IP | 74.200.28.144/28 |
| SPF_IP | 80.78.4.155 |
| SPF_IP | 80.78.4.156 |
| SPF_IP | 91.192.255.95 |
Related pages
Pivot deeper into the graph from bambora.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "bambora.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.