Hostname
jruby.org.s3.amazonaws.com
Last fetched
jruby.org.s3.amazonaws.com resolves to 16 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US.
Nutrition Label
Resolution chain
jruby.org.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.176.17 | 16.15.176.0/21 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 16.15.181.114 | 16.15.176.0/21 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 16.15.187.219 | 16.15.184.0/21 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 16.182.101.97 | 16.182.96.0/20 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 16.182.64.73 | 16.182.64.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 16.182.99.113 | 16.182.96.0/20 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.5.11.192 | 3.5.11.0/24 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.5.17.123 | 3.5.17.0/24 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.5.19.149 | 3.5.19.0/24 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.5.28.158 | 3.5.28.0/24 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.5.29.212 | 3.5.29.0/24 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.5.8.150 | 3.5.8.0/24 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.5.9.191 | 3.5.9.0/24 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.217.119.113 | 52.217.112.0/20 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 54.231.128.25 | 54.231.128.0/19 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 54.231.165.113 | 54.231.160.0/19 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
No WHOIS records are currently associated with jruby.org.s3.amazonaws.com in WhisperGraph.
Web-graph footprint
Distinct hostnames that link to or from jruby.org.s3.amazonaws.com in the public web crawl.
5 sites link to this hostname.
Threat posture
History
Related pages
Pivot deeper into the graph from jruby.org.s3.amazonaws.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "jruby.org.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.