Hostname
curiosity.com
Last fetched
curiosity.com resolves to 12 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US.
Nutrition Label
Resolution chain
curiosity.com 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 |
|---|---|---|---|---|
| 18.211.139.157 | 18.208.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 23.22.186.68 | 23.22.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.213.84.69 | 3.208.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.220.73.188 | 3.208.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.226.108.100 | 3.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.91.168.123 | 3.80.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.200.90.29 | 34.192.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.234.120.132 | 34.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 35.171.249.243 | 35.168.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.147.112.236 | 54.147.64.0/18 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.237.68.229 | 54.237.0.0/16 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 98.82.150.136 | 98.80.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
WHOIS identity
WHOIS data is temporarily unavailable. Refresh in a moment to retry.
Subdomains
Subdomain count is temporarily unavailable. Refresh in a moment to retry.
Web-graph footprint
Distinct hostnames that link to or from curiosity.com in the public web crawl.
Sample inbound links
Sample outbound links
Threat posture
History
Mail and authentication
SPF policy
6 SPF mechanisms authorising senders for curiosity.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 198.147.8.23 |
| SPF_IP | 198.147.9.14 |
| SPF_IP | 205.220.160.51 |
| SPF_IP | 205.220.172.51 |
Related pages
Pivot deeper into the graph from curiosity.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "curiosity.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.