Hostname
bmstesting.s3.amazonaws.com
Last fetched
bmstesting.s3.amazonaws.com resolves to 16 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US.
Nutrition Label
Resolution chain
bmstesting.s3.amazonaws.com 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.183.125 | 16.15.176.0/21 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 16.15.188.74 | 16.15.184.0/21 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 16.15.189.13 | 16.15.184.0/21 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 16.15.202.221 | 16.15.200.0/21 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 16.15.207.197 | 16.15.200.0/21 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.5.16.11 | 3.5.16.0/24 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.5.16.183 | 3.5.16.0/24 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.5.2.108 | 3.5.2.0/24 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.5.28.62 | 3.5.28.0/24 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.5.29.168 | 3.5.29.0/24 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.216.49.73 | 52.216.48.0/20 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.216.93.107 | 52.216.93.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.217.118.89 | 52.217.112.0/20 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.217.136.9 | 52.217.128.0/19 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.217.206.209 | 52.217.192.0/19 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.217.226.137 | 52.217.224.0/19 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
No WHOIS records are currently associated with bmstesting.s3.amazonaws.com in WhisperGraph.
Web-graph footprint
Distinct hostnames that link to or from bmstesting.s3.amazonaws.com in the public web crawl.
Sample inbound links
Threat posture
History
Related pages
Pivot deeper into the graph from bmstesting.s3.amazonaws.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "bmstesting.s3.amazonaws.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.