Hostname
rocky-api.prod.ltdev.io
Last fetched
rocky-api.prod.ltdev.io resolves to 19 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US.
Nutrition Label
Resolution chain
rocky-api.prod.ltdev.io resolves to 19 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 3.213.165.115 | 3.208.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.222.97.20 | 3.208.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.223.151.126 | 3.208.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.82.87.69 | 3.80.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.195.11.38 | 34.192.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.198.232.5 | 34.192.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.225.54.0 | 34.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 44.206.37.179 | 44.192.0.0/11 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 44.209.28.250 | 44.192.0.0/11 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 50.19.59.195 | 50.19.0.0/17 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.4.2.254 | 52.4.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.5.72.214 | 52.4.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.72.180.154 | 52.72.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.86.103.153 | 52.86.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.87.94.176 | 52.86.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.197.182.66 | 54.196.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.235.119.78 | 54.234.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.70.35.195 | 52.70.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 32.192.136.169 | 32.192.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
WHOIS identity
No WHOIS records are currently associated with rocky-api.prod.ltdev.io in WhisperGraph.
Threat posture
History
Related pages
Pivot deeper into the graph from rocky-api.prod.ltdev.io.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "rocky-api.prod.ltdev.io"})-[: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.