Hostname
tw.marcus.com
Last fetched
tw.marcus.com resolves to 18 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US.
Nutrition Label
Resolution chain
tw.marcus.com resolves to 18 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 184.72.196.66 | 184.72.128.0/17 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.81.160.250 | 3.80.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.81.34.98 | 3.80.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.92.73.37 | 3.80.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.94.118.33 | 3.80.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.227.69.208 | 34.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.228.226.208 | 34.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.235.157.96 | 34.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.238.142.137 | 34.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.202.183.71 | 52.200.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.203.10.175 | 52.200.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.71.250.50 | 52.70.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.91.10.195 | 52.90.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.157.191.63 | 54.156.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.166.175.19 | 54.166.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.84.25.71 | 54.84.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.87.65.139 | 54.87.0.0/16 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.92.181.121 | 54.92.128.0/17 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
WHOIS identity
No WHOIS records are currently associated with tw.marcus.com in WhisperGraph.
Subdomains
3 observed subdomains of tw.marcus.com.
Threat posture
History
Related pages
Pivot deeper into the graph from tw.marcus.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "tw.marcus.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.