Hostname
hypotheticallyfun.com
Last fetched
hypotheticallyfun.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
hypotheticallyfun.com resolves to 8 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 108.138.125.129 | 108.138.120.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 108.138.125.164 | 108.138.120.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 108.138.125.35 | 108.138.120.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 108.138.125.42 | 108.138.120.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 65.9.84.128 | 65.8.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IE |
| 65.9.84.187 | 65.8.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IE |
| 65.9.84.24 | 65.8.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IE |
| 65.9.84.6 | 65.8.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IE |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of hypotheticallyfun.com owner
- Contact emails
- 34c6e84f-c019-4a71-8bda-f6e1c9f9ae7f@identity-protect.org
- 6ac9a101-b47b-401c-bfd4-7880bcd06c54@identity-protect.org
- 87f6ce16-696d-40a7-af07-c8a9b7309931@identity-protect.org
- c4ac276b-20ed-49b7-a9c1-dbed759455c8@identity-protect.org
- owner-8590460@hypotheticallyfun.com.whoisprivacyservice.org
- owner@hypotheticallyfun.com.whoisprivacyservice.org
Threat posture
History
Related pages
Pivot deeper into the graph from hypotheticallyfun.com.
- IP · 108.138.125.129
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · US
- Email · 34c6e84f-c019-4a71-8bda-f6e1c9f9ae7f@identity-protect.org
- TLD · .com
- Browse hostnames · hy…
- 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: "hypotheticallyfun.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.