Hostname
data.mktg.universalhorrorunleashed.com
Last fetched
data.mktg.universalhorrorunleashed.com resolves to 13 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US.
Nutrition Label
Resolution chain
data.mktg.universalhorrorunleashed.com resolves to 13 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 63.140.38.204 | 63.140.38.0/23 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 63.140.38.38 | 63.140.38.0/23 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 63.140.38.59 | 63.140.38.0/23 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 63.140.38.61 | 63.140.38.0/23 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 63.140.38.77 | 63.140.38.0/23 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 63.140.39.145 | 63.140.38.0/23 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 63.140.39.146 | 63.140.38.0/23 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 63.140.39.214 | 63.140.38.0/23 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 63.140.39.25 | 63.140.38.0/23 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 63.140.39.87 | 63.140.38.0/23 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 63.140.48.110 | 63.140.48.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | SG |
| 63.140.48.217 | 63.140.48.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | SG |
| 63.140.48.235 | 63.140.48.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | SG |
WHOIS identity
No WHOIS records are currently associated with data.mktg.universalhorrorunleashed.com in WhisperGraph.
Threat posture
History
Related pages
Pivot deeper into the graph from data.mktg.universalhorrorunleashed.com.
- IP · 63.140.38.204
- ASN · AS14618AMAZON-AES - Amazon.com, Inc.
- Country · US
- Apex domain · universalhorrorunleashed.com
- Parent domain · mktg.universalhorrorunleashed.com
- TLD · .com
- Browse hostnames · da…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "data.mktg.universalhorrorunleashed.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.