Hostname
cloud.tourbuzz.net
Last fetched
cloud.tourbuzz.net resolves to 16 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US.
Nutrition Label
Resolution chain
cloud.tourbuzz.net resolves to 16 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 16.15.177.81 | 16.15.176.0/21 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 16.15.183.125 | 16.15.176.0/21 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 16.15.199.117 | 16.15.192.0/21 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 16.15.200.130 | 16.15.200.0/21 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 16.182.70.121 | 16.182.64.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.5.11.201 | 3.5.11.0/24 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.5.16.206 | 3.5.16.0/24 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.5.28.184 | 3.5.28.0/24 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.5.28.197 | 3.5.28.0/24 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.5.30.74 | 3.5.30.0/23 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.5.7.110 | 3.5.7.0/24 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.216.24.156 | 52.216.24.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.216.51.49 | 52.216.48.0/20 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.216.86.171 | 52.216.86.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 54.231.130.225 | 54.231.128.0/19 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 54.231.201.177 | 54.231.192.0/19 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
No WHOIS records are currently associated with cloud.tourbuzz.net in WhisperGraph.
Web-graph footprint
Distinct hostnames that link to or from cloud.tourbuzz.net in the public web crawl.
7 sites link to this hostname.
Threat posture
History
Related pages
Pivot deeper into the graph from cloud.tourbuzz.net.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "cloud.tourbuzz.net"})-[: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.