Hostname
jag.technology
Last fetched
jag.technology resolves to 12 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US. WHOIS lists iana:81 as the registrar.
Nutrition Label
Resolution chain
jag.technology resolves to 12 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 100.27.95.33 | 100.24.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 18.215.111.60 | 18.208.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.232.109.72 | 3.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.224.220.189 | 34.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.237.221.150 | 34.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 44.197.8.180 | 44.192.0.0/11 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.202.152.209 | 52.200.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.6.54.167 | 52.4.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.174.103.110 | 54.174.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.86.16.68 | 54.86.0.0/16 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.92.190.123 | 54.92.128.0/17 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 98.83.103.55 | 98.80.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:81
- Organization
- —
- Contact emails
Subdomains
1 observed subdomain of jag.technology.
| Subdomain |
|---|
| www.jag.technology |
Threat posture
History
Related pages
Pivot deeper into the graph from jag.technology.
- IP · 100.27.95.33
- ASN · AS14618AMAZON-AES - Amazon.com, Inc.
- Registrar · iana:81
- Country · US
- Email · 8a83527ef936eab324f830f63a1a5557-8993562@contact.gandi.net
- TLD · .technology
- Browse hostnames · ja…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "jag.technology"})-[: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.